Last modified by Ilie Andriuta on 2020/06/01

From version 17.3
edited by Vincent Massol
on 2020/01/27
Change comment: There is no comment for this version
To version 17.2
edited by Vincent Massol
on 2020/01/27
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -90,7 +90,7 @@
90 90  
91 91  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:
92 92  
93 -* The [[Velocity Java API changed quite a lot>>https://velocity.apache.org/engine/2.2/upgrading.html]], if you use advanced features directly in Java there is a big chance that you need to update your code.
93 +* 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
94 94  * 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.
95 95  * We tried to reduce as much as possible the breaking changes in the language using some retro compatibility flags provided by Velocity and some hacks on XWiki side but there is still things for which you might want to be carefull:
96 96  ** Deprecations: A lot of APIs are now deprecated, they should work fine but will produce a warning in the log (unless you disabled that using the new property ##logging.deprecated.enabled## in ##xwiki.properties##)

Get Connected