[ http://jira.codehaus.org/browse/MRELEASE-128?page=comments#action_67977 ]
Martin Gilday commented on MRELEASE-128:
----------------------------------------
I posted a question regarding this on the maven users mailing list. At least
now I know it appears to be a bug and not my POM.
But I get the problem when using release:perform as well. Do I need to create
another issue for this (quite new to JIRA/reporting)?
Another slight difference is that my property is for the SCM username and
password - $\{cvs-user\} and $\{cvs-pass\}. After a release:perform both of
these properties are replaced with the ones from the settings.xml. I have
tried removing the properties from the POM and specifiying them with \
-Dusername and \-Dpassword. Doing this also reasults in the SCM path being
altered and the login details added. Both the exported POM and the original
POM are incorrectly altered.
{code:xml}
<scm>
<connection>scm:cvs:pserver:${cvs-user}:[EMAIL
PROTECTED]:/usr/share/cvs/cvsroot:MyProjectName</connection>
<developerConnection>scm:cvs:pserver:${cvs-user}:[EMAIL
PROTECTED]:/usr/share/cvs/cvsroot:MyProjectName</developerConnection>
</scm>
{code}
turns to
{code:xml}
<scm>
<connection>scm:cvs:pserver:joebloggs:[EMAIL
PROTECTED]:/usr/share/cvs/cvsroot:MyProjectName</connection>
<developerConnection>scm:cvs:pserver:joebloggs:[EMAIL
PROTECTED]:/usr/share/cvs/cvsroot:MyProjectName</developerConnection>
</scm>
{code}
after the release:perform is called.
> SCM properties being replaced during release:perform
> ----------------------------------------------------
>
> Key: MRELEASE-128
> URL: http://jira.codehaus.org/browse/MRELEASE-128
> Project: Maven 2.x Release Plugin
> 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
