[jira] Commented: (MNG-4140) Properties incorrectly replaced in pom
[
http://jira.codehaus.org/browse/MNG-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=182860#action_182860
]
John Casey commented on MNG-4140:
-
See:
http://docs.codehaus.org/display/MAVEN/Artifact-Coordinate+Expression+Transformation
> 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.2.0
>
> 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
[jira] Commented: (MNG-4140) Properties incorrectly replaced in pom
[
http://jira.codehaus.org/browse/MNG-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=182835#action_182835
]
Jean-Marc Borer commented on MNG-4140:
--
Why is this an issue? Shouldn't the pom included in the jars being
interpolated? I am missing something here... any insights?
> 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.2.0
>
> 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
[jira] Commented: (MNG-4140) Properties incorrectly replaced in pom
[
http://jira.codehaus.org/browse/MNG-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181768#action_181768
]
Benjamin Bentmann commented on MNG-4140:
For the record, POM interpolation upon installation/deployment to repos has
been completely removed from Maven 2.2.
> 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.2.0
>
> 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
[jira] Commented: (MNG-4140) Properties incorrectly replaced in pom
[
http://jira.codehaus.org/browse/MNG-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174338#action_174338
]
John Casey commented on MNG-4140:
-
NOTE: I've revised the fix for this issue to be JDK 1.4 compatible. Note also
that when using JDK 1.4, your POMs WILL NOT BE INTERPOLATED for version
expressions on install/deploy...however, the build will still run on 1.4. You
should use JDK 1.5+ if you plan to use this feature.
> 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
[jira] Commented: (MNG-4140) Properties incorrectly replaced in pom
[
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
".+" 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
