[ http://jira.codehaus.org/browse/MRELEASE-128?page=comments#action_74301 ] Eric Bernstein commented on MRELEASE-128: -----------------------------------------
I'm attaching a possible fix for this issue to MRELEASE-114. I had meant to post it here (which is why it's named as such), but apparently I have issue keeping track of my firefox tabs. The below notes are identical to my comments on MRELEASE-114. Some notes: 1. 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. 2. 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. > SCM properties being replaced during release:perform > ---------------------------------------------------- > > Key: MRELEASE-128 > URL: http://jira.codehaus.org/browse/MRELEASE-128 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4 > Reporter: Craig Dickson > Attachments: after-release-perform-pom.xml, > after-release-prepre-pom.xml, original-pom.xml > > > The <scm> section of a pom in CVS for a pom archetype project looks like this > prior to executing release:prepare : > <scm> > <connection>${base.cvs.url}:commons-maven/uber-pom</connection> > > <developerConnection>${base.cvs.url}:commons-maven/uber-pom</developerConnection> > <url>${base.viewcvs.url}/commons-maven/uber-pom</url> > </scm> > Then after executing release:prepare, the pom in CVS looks like this (new > <tag> tag is only difference): > <scm> > <connection>${base.cvs.url}:commons-maven/uber-pom</connection> > > <developerConnection>${base.cvs.url}:commons-maven/uber-pom</developerConnection> > <url>${base.viewcvs.url}/commons-maven/uber-pom</url> > <tag>R-1_7</tag> > </scm> > Then after executing release:perform, the pom looks like this in CVS: > <scm> > > <connection>scm:cvs:pserver:behrcvs.masco-coatings.com:/usr/cvsroot:commons-maven/uber-pom</connection> > > <developerConnection>scm:cvs:pserver:behrcvs.masco-coatings.com:/usr/cvsroot:commons-maven/uber-pom</developerConnection> > > <url>http://behrcvs.masco-coatings.com/cgi-bin/viewcvs.cgi/commons-maven/uber-pom</url> > </scm> > Notice that the properties that were there for the base URLs for CVS and > ViewCVS have been replaced with literal values. > No other properties in the POM are being replaced -- 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
