[ https://issues.apache.org/jira/browse/VELOCITY-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claude Brisson reopened VELOCITY-904: ------------------------------------- Ok, I'll have a look at it. To answer your question about what you can do to help speed up the release process, well, all the tests and regressions that you do discover are certainly helpful to improve the quality of the release, especially about backward compatibility, and we thank you for them, but I'm not sure they're making the release process faster... I can't also help thinking that your use of null macro arguments is somewhat a corner case of macro usages which is very specific to xwiki, but at least it makes xwiki a good regression candidate. > Add a flag for better backward compatibility with null macro arguments > ---------------------------------------------------------------------- > > Key: VELOCITY-904 > URL: https://issues.apache.org/jira/browse/VELOCITY-904 > Project: Velocity > Issue Type: Improvement > Components: Engine > Affects Versions: 2.0 > Reporter: Claude Brisson > Assignee: Claude Brisson > Priority: Minor > Fix For: 2.2 > > > See [this > comment|https://issues.apache.org/jira/browse/VELOCITY-542?focusedCommentId=16621819&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16621819] > : > {code} > #macro(testmacro $parameter) > $parameter > #end > #testmacro($return) > {code} > bq. which used to print "$return" (when $return is null or undefined) and we > now get "$parameter". > -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org