[
http://jira.codehaus.org/browse/MNG-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253734#action_253734
]
luke w patterson commented on MNG-4998:
---------------------------------------
what about using a new expression like ${project.properties.myProperty} ?
in the <plugin> <configuration> section, it will be resolved dynamic/lazy
in other sections either:
* not interpolated (evaluates to the original string of
"${project.properties.myProperty}")
* it is resolved static/eager
the existing references to ${myProperty} would be resolved just like they are
now
> Variables interpolation: dynamic in Maven 2, static in Maven 3
> --------------------------------------------------------------
>
> Key: MNG-4998
> URL: http://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.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
