[
http://jira.codehaus.org/browse/MNG-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253921#action_253921
]
luke w patterson commented on MNG-4998:
---------------------------------------
maybe ${project.properties.myProperty} could be initialized if ${myProperty}
isn't null
how about -
for non-<plugin><configuration> sections:
* ${project.properties.myProperty} is evaluated static/eager to whatever
${myProperty} evaluates to
* if ${myProperty} is null, then it is left as
"${project.properties.myProperty}"
for <plugin><configuration> sections:
* ${project.properties.myProperty} is initialized with whatever ${myProperty}
evaluates to
* plugins can override the initial value
* the "effective-pom"/pre-run interpolation always sees/displays it as
"${project.properties.myProperty}"
> 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
