maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Gleissner (JIRA)" <>
Subject [jira] Commented: (MNG-4998) Variables interpolation: dynamic in Maven 2, static in Maven 3
Date Thu, 13 Oct 2011 02:53:09 GMT


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.


> Variables interpolation: dynamic in Maven 2, static in Maven 3
> --------------------------------------------------------------
>                 Key: MNG-4998
>                 URL:
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: POM
>    Affects Versions: 3.0.2
>            Reporter: Evgeny Goldin
> Please, see
> 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:


View raw message