[
http://jira.codehaus.org/browse/MRELEASE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93448
]
Ian Springer commented on MRELEASE-114:
---------------------------------------
I had ${maven.username} is the value of scm.developerConnection, and it was
resolved and replaced in both the "prepare release X.Y.Z" POM and the "prepare
for next development iteration" POM. I think this is incorrect behavior in both
cases, but particularly undesirable in the latter case... Will this be fixed in
the next release?
> ${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
> 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
