[jira] [Resolved] (VELOCITY-752) Evaluation of macro arguments

[ https://issues.apache.org/jira/browse/VELOCITY-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Brisson resolved VELOCITY-752. - Resolution: Fixed Assignee: Claude Brisson Fix Version/s: 2.x Fixed by

[jira] [Resolved] (VELOCITY-684) Passing a map literal to a macro call forbids altering the map in any way, while maps bound to an actual parameter may be changed

[ https://issues.apache.org/jira/browse/VELOCITY-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Brisson resolved VELOCITY-684. - Resolution: Fixed Assignee: Claude Brisson Fix Version/s: 2.x Fixed by

[jira] [Resolved] (VELOCITY-683) When passing literals other than strings to macro calls, setting new values the formal parameters does not propagate the changes outside the local scope

[ https://issues.apache.org/jira/browse/VELOCITY-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Brisson resolved VELOCITY-683. - Resolution: Fixed Assignee: Claude Brisson Fix Version/s: 2.x Fixed by

Re: Macro arguments

The sharing convention is already in place since I applied Jarkko's patch from VELOCITY-841 (which I applied in commit 1753788). You're right, I think we don't need to go further. So I guess we're ready for the release! Claude On 13/09/2016 23:40, Nathan Bubna wrote: Since you're