VPP CHANGES 2.2.0 - 02/05/2004 - New features: - Velocity Context tools can now be configured by referencing a configured data type. This means that the tool can be configured in the build file using Ant's configuration conventions - Added Velocity event handler support. Event handlers can be configured just like tools making them flexible and easy to use. - Included a useful event handler, VPPFailOnNullInsertion, which throws BuildException if an attempt is made to insert the value of an undefined reference. - Added an 'add' attribute to the property element of VPPEngine. This supports the ability to configure multi-value Velocity Engine properties such as resource loader paths. - Updated documentation for the above and fixed a few typos. 2.1.2 - 02/03/2004 - Updated the documentation to reflect the correct keys used to configure the default Velocity Engine. 2.1.1 - 01/22/2004 - Fixed documentation typos. 2.1.0 - 01/14/2004 - Added VPPTool. - VPPCopy and VPPJavac now automatically insert an instance of VPPTool, which provides access to source and destination file information, e.g. source name, size, etc. This tool is accessible through the key 'vpp'. - Fixed numerous documentation typos. - Updated examples for change that was made to the way Ant 1.6.0 namespaces are used to identify subelements of a task. In Ant 1.6.0b3, subelements did not have to be qualified, but as of 1.6.0, they do. 2.0.0 - 12/04/2003 - Major overhaul of VPP. Main changes were to: - Support Ant 1.6 antlib - Support nested elements of filters in Ant 1.6 - Added a data type called VPPConfig which can be defined standalone or as a nested element of any vpp task. Its purpose is to better organize the configuration of the Velocity Context and Engines. - Removed the velocityProperty nested element. Use a VPPConfig nested element instead. - Added support to allow user defined tools to be added to a Velocity Context. - Renamed vpp to vppcopy. - Added much more documentation. 1.2.2 - 02/03/2003 - Fixed some minor bugs. 1.2.0 - 01/21/2003 - Changed the license to BSD. - Now providing the ant project in the velocity context accessed using $project. $ant is still available, but will be removed in a future release. Use $project.getProperty("propertyName") instead. - Changed the types used for configuring the velocity engine and context. Now there is engine, string, and class, in place of the velocityProperty. Engine properties are used to initialize the VelocityEngine. String and class type properties are used to populate the VelocityContext. 1.1.0 - 12/16/2002 - Added support for configuring the VelocityEngine. 1.0.0 - 12/16/2002 - Initial public release on sourceforge.