[
http://jira.codehaus.org/browse/MNG-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99673
]
Kenney Westerhof commented on MNG-2339:
---------------------------------------
This issue deals with ${project.version}, or ${version}, or ${xxx.version} for
that matter, all being treated like ${version}.
commandline arguments like -Dversion=foo will have effect on the dependencies
or wherever one of the expressions above is used.
${project.version} and ${pom.version} should ALWAYS resolve to a <version> tag
in the pom.
RegexBasedModelInterpolator strips off the first part (project.) and then
checks the context for the value. This is wrong.
Issue MNG-2486 is different - that one deals with the fact that SNAPSHOT
version expressions, which are correctly interpolated from the pom and not from
external properties,
are evaluated to the timestamped version instead of the string present in the
model.
> ${project.*} are interpreted in the wrong place
> -----------------------------------------------
>
> Key: MNG-2339
> URL: http://jira.codehaus.org/browse/MNG-2339
> Project: Maven 2
> Issue Type: Bug
> Components: General
> Affects Versions: 2.0.4
> Reporter: Emmanuel Venisse
> Assignee: Kenney Westerhof
> Priority: Critical
> Fix For: 2.0.8
>
>
> If a plugin use ${project.version}, this parameter is interpreted with the
> version of the current project and not the plugin version. I think we have
> the same pb with dependencies and other ${project.*}
> For a plugin in version 2.0 used in a project in version 1.0-SNAPSHOT,
> ${project.version} used in the plugin will be interpreted as 1.0-SNAPSHOT
> instead of 2.0
--
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
