The Apache Software Foundation

The Apache Velocity project is pleased to announce the release of VelocityTools 2.0.

Downloads are available here:
 http://velocity.apache.org/download.cgi

This should be useable as a drop in replacement for Tools 2.0-beta4 or Tools 1.4, with a few minor exceptions.  The 2.x series of VelocityTools requires Velocity 1.5+ and JDK 1.5+.

For those new to Tools 2, here's an overview of the work done since 1.4:
   * More convention over configuration and smart defaults
   * New configuration formats (more concise/flexible/powerful xml, properties, java)
   * Provision of default and auto-loaded configurations
   * Entirely new core infrastructure (lazy-loading tools, easier access, standalone support etc)
   * Added VelocityViewTag for JSP integration
   * Added DisplayTool, ConversionTool, ClassTool, LoopTool, FieldTool, a generic version of LinkTool and more
   * Refactored and enhanced a number of existing tools
   * Improved documentation
   * Deprecated many outdated things
   * Legacy support for almost all Tools 1.4 configurations and extensions
   * Better integration of $application, $session and $request scope control objects
   * and lots more...

For those following the betas, here's the notable changes since 2.0-beta4:
   * Added a 'readOnly' config option to allow write operations on ValueParser and ParameterTool (when set to false)
   * Added a beta-quality UiDependencyTool (included in velocity-view, but not in default tools.xml)
   * Added an alpha-quality MarkupTool (included in generic tools, but not in default tools.xml)
   * Fixed (as much as possible) some significant last-iteration LoopTool problems, and added a loop.this property to serve as a more reliable workaround in nested loops. See
https://issues.apache.org/jira/browse/VELTOOLS-124
   * VelocityLayoutServlet now checks request attributes for non-default layouts.
   * The velocity-view.tld is now valid.
   * VelocityView[Servlet] has improved exception and http management (particularly for ResourceNotFoundExceptions).
   * Miscellaneous documentation and build.xml improvements

The Velocity developers are very interested in all feedback regarding Tools 2.0, especially regarding backwards compatibility with apps designed for Tools 1.4 or earlier. We aim to enable a smooth,
incremental transition for developers and their applications.

The Apache Velocity Team announces the availability of the of Apache Velocity Engine 1.6.4. This is only a bugfix release and contains no new features.  We recommend all 1.6.x users upgrade to this release.

The change log is here:
http://velocity.apache.org/engine/releases/velocity-1.6.4/changes-report.html

Apache Velocity 1.6.4 can be downloaded here:
http://velocity.apache.org/download.cgi

Documentation for Engine1.6.4 can be found here:
http://velocity.apache.org/engine/releases/velocity-1.6.4/

For the Apache Velocity Team

아파치 Velocity 개발자들이 Velocity Engine 1.7-beta1을 발표하였습니다.
The Velocity developers are please to announce the availability of Velocity Engine 1.7-beta1.

관련 파일은 아래 주소에서 다운로드 받을 수 있습니다.
Downloads can be found here:
 http://velocity.apache.org/download.cgi

A great deal of work has been done since the 1.6 branch.
1.6까지는 여러가지 작업들을 진행해왔습니다.  

Here's a taste:
- Your macros can now be called with bodies when you want:
    #macro(foo)Here is $bodyContent#end
    #@foo()body content!#end

- Quotes can be escaped in strings by doubling them:
    #set( $foo = "$person said, ""$comment"" " )
    #set( $bar = 'Joe said, ''Hi!'' ' )

- The flawed #literal directive has been replaced with:
    #[[ This is included but not parsed, so #if and $foo need no escaping.]]#

Also included are namespacing improvements, better #break and #stop, bracketed index syntax, and more!  For full details, please see the

change log:
 http://velocity.apache.org/engine/devel/changes-report.html

This should work as a drop-in replacement for Velocity 1.6.3 in the vast majority of cases.  However, there have been a number of deprecations (should result in warnings in your log output) and a few
minor behavioral changes, all of which are explained in the change log. :)