Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ThomasMortagne
	1	+XWiki.surli

Content

...	...	@@ -21,7 +21,6 @@
21	21	The following runtime dependencies have been upgraded (they have a different release cycle than [[XWiki Commons>>http://commons.xwiki.org]], [[XWiki Rendering>>http://rendering.xwiki.org]] and [[XWiki Platform>>http://platform.xwiki.org]]):
22	22
23	23	* [[CSS4J 2.0.0>>https://jira.xwiki.org/browse/XWIKI-16905]]
24		-* [[Jodconverter 4.2.3>>https://jira.xwiki.org/browse/XWIKI-16973]]
25	25
26	26	= Translations =
27	27
...	...	@@ -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
	78	+*** 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