[
http://jira.codehaus.org/browse/MNG-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=173583#action_173583
]
John Casey commented on MNG-4140:
---------------------------------
sorry, not sure what I was thinking on this one. It's simply searching for any
"<version>.+</version>" and interpolating the value...which has obvious
side-effects for plugin configurations. I'm working on an xpath solution now
that will allow us to preserve xml comments, etc. in the original POM, without
the need to drag in additional dependencies.
> Properties incorrectly replaced in pom
> --------------------------------------
>
> Key: MNG-4140
> URL: http://jira.codehaus.org/browse/MNG-4140
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Reinhard Nägele
> Assignee: John Casey
> Priority: Critical
> Fix For: 2.1.1
>
> Attachments: pom-transformed.xml, pom.xml
>
>
> The attached sample pom configures the dependency plugin. During an install,
> {{$\{project.version\}}} is replaced by the actual version when in fact no
> replacement at all must happen (see {{pom-transformed.xml}}). This seems to
> be related to the {{version}}, since all other properties remain unchanged.
> In our real world scenario, the dependency plugin is configured in a profile
> in order to copy child module artifacts to Luntbuild's publish directory.
> This, of course, won't work if the version is replaced during install. It
> must be evaluated at runtime.
> This is a regression in Maven 2.1.0. Maven 2.0.10 does not have the problem.
--
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
