[
https://jira.codehaus.org/browse/MNG-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=281177#comment-281177
]
Christian Gleissner commented on MNG-4998:
------------------------------------------
Hi Luke,
your suggestion seems to be a good compromise between the Maven 2 behavior and
how Maven 3.0.x handles properties. I would very much appreciate if the Maven 2
ability to redefine properties could be preserved for Maven 3. As you
mentioned, the properties section could then be used for defining defaults
which specific plugins may chose to override, only visible within their local
configuration contexts. Evgeny's approach to use Groovy snippets for this is
very innovative and I'd like to use this in Maven 3.
Thanks
Christian
> Variables interpolation: dynamic in Maven 2, static in Maven 3
> --------------------------------------------------------------
>
> Key: MNG-4998
> URL: https://jira.codehaus.org/browse/MNG-4998
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: POM
> Affects Versions: 3.0.2
> Reporter: Evgeny Goldin
>
> Please, see
> http://maven.40175.n5.nabble.com/Variables-interpolation-dynamic-in-Maven-2-static-in-Maven-3-td3360336.html.
> It demonstrates two examples where expression with ${variables} are
> interpolated differently in Maven 2 and Maven 3: Maven 2 allows to update
> <properties> and effect expressions interpolated later, Maven 3 also allows
> to update <properties> but all expressions are interpolated with their old
> values.
> I believe Maven 2 dynamic behavior is much more preferable than Maven 3
> Ant-like "stickiness" to what's defined in <properties>.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
