[MRELEASE-487] release:prepare mojo corrupts ${} variable reference in the <scm> tag

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0-beta-7
• Component/s: prepare
• Labels: properties
• Environment: windows-xp; maven 2.1.0; cvs
• Assignee: Brett Porter
• Reporter: Andrew Woodford
• Created: 21/Sep/09 06:57
• Updated: 25/Jun/11 03:33
• Resolved: 23/Sep/10 05:02

Description

We have a parent pom which is used for inheritance. We would like the <scm> tag to be inherited by child projects (not modules) and have entered the following.

<scm>
    <connection>scm:cvs:ext:myhost:/repository:Projects/${project.artifactId}</connection>
</scm>

The problems is that the ${project.artifactId} variable is expanded during the release:prepare operation. It appears to happen in the writing of the next snapshot release version of the pom. i.e. The released pom (1.0) still contains the variable reference but new snapshot version (1.1-SNAPSHOT) has the expanded value. e.g...

<scm>
    <connection>scm:cvs:ext:myhost:/repository:Projects/myArtifactId</connection>
</scm>

This forces us to place the scm tag in all child poms which we'd prefer not to do.

cheers

Issue Links

• duplicates: MRELEASE-128 SCM properties being replaced during release:perform