This is an automated email from the ASF dual-hosted git repository.

cbrisson pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/velocity-site.git


The following commit(s) were added to refs/heads/main by this push:
     new e053846  Tweak upgrading page
e053846 is described below

commit e0538460d86e4d4a257dbd0c708385526f7cf57b
Author: Claude Brisson <[email protected]>
AuthorDate: Sat Aug 24 11:58:21 2024 +0200

    Tweak upgrading page
---
 src/content/engine/devel/upgrading.mdtext | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/src/content/engine/devel/upgrading.mdtext 
b/src/content/engine/devel/upgrading.mdtext
index 6a98911..9c4532c 100644
--- a/src/content/engine/devel/upgrading.mdtext
+++ b/src/content/engine/devel/upgrading.mdtext
@@ -40,7 +40,17 @@ To maximize backward compatibility of the last Velocity 2.x 
with Velocity 1.x, b
     # Let the range operator expressions '[ x..y ]' return mutable lists 
(since 2.4)
     runtime.immutable_ranges = false
 
-Also, please note that since version 2.1, Velocity requires Java JDK 1.8+ for 
bulding and Java JRE 1.8+ at runtime.
+Also, please note that since version 2.1, Velocity requires Java JDK 1.8+ for 
building and Java JRE 1.8+ at runtime.
+
+## Upgrading from Velocity 2.3 to Velocity 2.4
+
+### Behavior / API Changes
+
++ New 1.7.x backward compatibility configuration flag 
`runtime.immutable_ranges`
+
+### VTL Changes
+
++ With the `runtime.immutable_ranges=false` configuration, the VTL range 
operator `[x..y]` returns a mutable list.
 
 ## Upgrading from Velocity 2.2 to Velocity 2.3
 

Reply via email to