Last modified by Ilie Andriuta on 2020/06/01

<
From version < 4.1 >
edited by Thomas Mortagne
on 2020/01/20
To version < 6.1 >
edited by Thomas Mortagne
on 2020/01/22
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -66,7 +66,7 @@
66 66  
67 67  === Velocity 2.2 upgrade ===
68 68  
69 -After more than 9 years Velocity is getting an update. While this bring some nice new things it also comes with unavoidable behavior changes that might be a breackage for your scripts or break some extensions:
69 +While Velocity upgrade bring a lot of nice new improvements it also comes with unavoidable behavior changes that might be a breackage for your scripts or break some extensions:
70 70  
71 71  * The Velocity Java API changed quite a lot, if you use advanced features directly in Java there is a big chance that you need to update your code. You can find more details on https://velocity.apache.org/engine/2.2/upgrading.html
72 72  * Most names of Velocity configuration properties have changed ; old names are still functional but will emit a deprecation warning in the log. See the [[Configuration Changes in Velocity 2.1>>https://velocity.apache.org/engine/2.2/configuration-property-changes-in-2.1.html]] page.
... ... @@ -76,7 +76,7 @@
76 76  *** $sorttool replaced by $collectiontool
77 77  *** $velocityCount and $velocityHasNext where already deprecated in Velocity 1.7 without producing any deprecation warning, they now do
78 78  ** Breackages:
79 -*** No more macro semi-local context: in Velocity 1.7 variable set inside a macro and set both in the global context and in a special local context. In Velocity 2.x this local context does not exist anymore. In pratice in means that if in your macro you #set a variable and execute another Velocity template which set the same variable your macro will be affected while it used to be "protected" by the previous explicit #set
79 +*** No more Velocity macro semi-local context: in Velocity 1.7 variable set inside a macro were set both in the global context and in a special macro local context. In Velocity 2.x this local context does not exist anymore. In pratice in means that if, in your macro, you #set a variable and execute another Velocity template which set the same variable your macro will be affected while it used to be "protected" by the previous explicit #set. It's now (since Velocity 1.7 actually) recommended to use the $macro map to manipulate local variable (as in {{code}}#set($macro.myLocalVar = "value"){{/code}}).
80 80  ** Known bugs:
81 81  *** Macro parameters names mess with expression passed to the macro: see https://issues.apache.org/jira/browse/VELOCITY-904?focusedCommentId=17019513&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17019513. Should be fixed in 12.0 final.
82 82  

Get Connected