[ http://jira.codehaus.org/browse/MRELEASE-114?page=comments#action_78409 ] Jurgen Lust commented on MRELEASE-114: --------------------------------------
I checked out the 2.0-beta-4 tag of the maven-release-plugin and applied the patch supplied here, but the problem remains: ${user.name} and ${artifactId} are being replaced in the scm section and committed to svn... > ${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