[ http://jira.codehaus.org/browse/MRELEASE-114?page=all ]
Eric Bernstein updated MRELEASE-114:
------------------------------------
Attachment: MRELEASE-128-maven-release-plugin.patch
I'm attaching a possible fix for this issue.
Some notes:
# I made the assumption that the only reason we rewrite the scm config is for
subversion. This is quite possibly not the case, but it passed all the unit
tests and made my CVS scm do what I wanted it to. This is probably not the way
it should be implemented, but I don't know enough about the other SCMs to know
if the rewrite is a special case or the non-rewrite is a special case.
# This is a patch from the 2.0-beta-4 tag because the trunk didn't install
cleanly on checkout - it may or may not be easily portable to the trunk.
> ${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
