You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Wayne Fay (JIRA)" <ji...@codehaus.org> on 2007/02/08 08:02:44 UTC
[jira] Commented: (MNG-2651) POM interpolator treats
${pom.something} like ${something} and prefers system properties
[ http://jira.codehaus.org/browse/MNG-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87052 ]
Wayne Fay commented on MNG-2651:
--------------------------------
This seems to be the root cause behind numerous other bugs posted in JIRA...
MNG-2288
MNG-2339
MNG-2486
MNG-2653
It is also the cause for quite a lot of emails on the Maven Users list over the last year. :(
> POM interpolator treats ${pom.something} like ${something} and prefers system properties
> ----------------------------------------------------------------------------------------
>
> Key: MNG-2651
> URL: http://jira.codehaus.org/browse/MNG-2651
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
> Affects Versions: 2.0.4
> Reporter: Daniel Schulz
> Assigned To: Jason van Zyl
>
> The POM interpolator (RegexBasedModelInterpolator) removes all leading "pom.", "project." and "env." portions of an expression before evaluating it. then searching for values happens in the following order: system properties, project properties, pom bean properties.
> An example: Although ${pom.version} is more specific than ${version}, version wins. That's the problem in MNGECLIPSE-20.
> IMHO the interpolation strategy should be changed.
--
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