Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
None
-
Windows XP client, Linux repo, CVS, Maven 2.0.4
-
Patch
Description
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
Attachments
Attachments
Issue Links
- is duplicated by
-
MRELEASE-325 The release plugin does not keep the variable substitution in the connection/developer url after a release prepare/perform.
- Closed
-
MRELEASE-487 release:prepare mojo corrupts ${} variable reference in the <scm> tag
- Closed
-
MRELEASE-357 mutable CVS User
- Closed
-
MRELEASE-342 Can I get release plugin to not modify trunk pom's scm/connection and scm/url elements during prepare/perform? (version ok to modify)
- Closed
- is related to
-
MRELEASE-466 Release plugin should preserve pom properties and ${...} variables
- Closed
- relates to
-
MRELEASE-16 release-pom is changed too much
- Closed
-
MRELEASE-114 ${project.artifactId} was replaced with it's value during release:perform
- Closed
-
MRELEASE-389 Properties releaseVersion and developmentVersion are not read correctly during release:prepare (eventually release:perform)
- Closed