[
http://jira.codehaus.org/browse/MRELEASE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=202127#action_202127
]
Havard Bjastad commented on MRELEASE-114:
-----------------------------------------
Emmanuel, you're saying "Already fixed", but we're still seeing this problem
with Maven 2.0.9. There are also open issues on this, e.g. MRELEASE-128 and
MRELEASE-325, what exactly is fixed here, as opposed to the other ones?
> ${project.artifactId} was replaced with it's value during release:perform
> -------------------------------------------------------------------------
>
> Key: MRELEASE-114
> URL: http://jira.codehaus.org/browse/MRELEASE-114
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Environment: Windows XP, Java 1.4.2
> Reporter: Paul Spencer
> Assignee: Emmanuel Venisse
> Fix For: 2.0-beta-5
>
> Attachments: MRELEASE-128-maven-release-plugin.patch
>
>
> In release:perform, the variable ${project.artifactId} was replaced with it's
> value in the connection and developerConnection tags in the pom. This did NOT
> happen in other place in the pom!
> Before release:
> <connection>scm:cvs:pserver:[email protected]:/bar:${project.artifactId}</connection>
> After release:
> <connection>scm:cvs:pserver:[email protected]:/bar:master-pom</connection>
> BTW: The issue http://jira.codehaus.org/browse/MRELEASE-16 may be
> related to the above 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
