+1 Works well for me.
######
From a previous email:
Looking at the release notes:
* Deprecation of some VTL syntax constructs: the formal reference
notation |${...}| is now preferred for non-bare references (|$foo|
is still fine, but |$foo.bar| should be rewritten as |${foo.bar}|).
Deprecation warnings are off by default; the next minor release will
turn them on by default, and the next major release will remove
support for those deprecated forms.
I enabled runtime.deprecation.warn=true, to see the warnings, there are
hundreds :
2026-06-16 08:19:17,094 WARN org.apache.velocity.rendering
ASTReference:init - the informal notation '$utils.formatDate($utils.now,
$text.get("date.toStringFormat"))' is deprecated in output; use the
formal notation ${...} instead [line 634, column 21]
This is a very big change, adding ${} to 95% of our velocity statements.
Going forward > 2.5 is this change necessary or can it be ignored?
On 18/06/2026 12:40, Claude Brisson via dev wrote:
The Velocity Engine 2.5 RC1 test build has been available since June
14th.
Release notes:
*
https://dist.apache.org/repos/dist/dev/velocity/velocity-engine/2.5/release-notes.html
Distribution:
* https://dist.apache.org/repos/dist/dev/velocity/velocity-engine/2.5/
Maven 2 staging repository:
*
https://repository.apache.org/content/repositories/orgapachevelocity-1050/
Documentation:
* https://velocity.apache.org/engine/2.5/
Sources:
* https://github.com/apache/velocity-engine/releases/tag/2.5-RC1
If you have had a chance to review the test build, please respond with
a vote on its quality:
[ ] Leave at test build
[ ] Alpha
[ ] Beta
[ ] General Availability (GA)
Everyone who has tested the build is invited to vote. Votes by PMC
members are considered binding. A vote passes if there are at least
three binding +1s and more +1s than -1s.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
