[
http://jira.codehaus.org/browse/MRELEASE-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MRELEASE-487.
---------------------------------
Resolution: Duplicate
Assignee: Brett Porter
> release:prepare mojo corrupts ${} variable reference in the <scm> tag
> ---------------------------------------------------------------------
>
> Key: MRELEASE-487
> URL: http://jira.codehaus.org/browse/MRELEASE-487
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-7
> Environment: windows-xp
> maven 2.1.0
> cvs
> Reporter: Andrew Woodford
> Assignee: Brett Porter
>
> 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.
> {noformat}
> <scm>
>
> <connection>scm:cvs:ext:myhost:/repository:Projects/${project.artifactId}</connection>
> </scm>
> {noformat}
> 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...
> {noformat}
> <scm>
>
> <connection>scm:cvs:ext:myhost:/repository:Projects/myArtifactId</connection>
> </scm>
> {noformat}
> This forces us to place the scm tag in all child poms which we'd prefer not
> to do.
> cheers
--
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
