[ http://jira.codehaus.org/browse/MRELEASE-114?page=comments#action_78411 ]
Eric Bernstein commented on MRELEASE-114:
-----------------------------------------
Yes, Jurgen, that's where my patch falls short (see point 1 on my notes above).
I knew SVN needed some form of rewrite (for tagging, etc...) and CVS (and
others) did not. Not being very familiar with SVN, I kept the SVN
functionality the same and exempted the other SCMs so that I would, at worst,
do no harm.
If you have a better understanding of SVN, I imagine the patch could be
improved by manipulating the URLs as they should be using the base URLs rather
than the evaluated URLs as I believe they are today.
> ${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
