release:branch is altering poms on the tag hierarchy
----------------------------------------------------
Key: MRELEASE-612
URL: http://jira.codehaus.org/browse/MRELEASE-612
Project: Maven 2.x Release Plugin
Issue Type: Bug
Affects Versions: 2.1, 2.0
Reporter: Frédéric Camblor
Currently, I execute following command line :
mvn --batch-mode org.apache.maven.plugins:maven-release-plugin:2.0:branch
-DautoVersionSubmodules=true -DtagBase=tags/ -Dtag=1.0.0
-DupdateBranchVersions=true -DreleaseVersion=2.0.0 -DbranchBase=branches/
-DbranchName=2.0.0
My goal, here, is to create a new branch called "2.0.0" from the 1.0.0 tag.
It works great but I found something crappy : some commit were made on the
1.0.0 tag hierarchy.
That is to say, the plugin is acting this way :
- Checkout tag ${tagBase}${tag} in working directory
- Modify pom to ${releaseVersion}-SNAPSHOT & scm
- Commit pom (on tag 1.0.0 !!!)
--------- If something is going bad during the next two lines, your tag
hierarchy will be altered
- SVN Copy ${tagBase}${tag}/ hierarchy to ${branchBase}${branchName}/ hierarchy
- Re-Modify pom in working directory to ${tag}
- Re-Commit pom on tag 1.0.0
I would think it would act this way :
- SVN Copy ${tagBase}${tag}/ hierarchy to ${branchBase}${branchName}/ hierarchy
- Checkout ${branchBase}${branchName}/ in working directory
- Modify pom to ${releaseVersion}-SNAPSHOT
- Commit pom (on branch !) & scm
Even by passing -DupdateWorkingCopyVersions=false, it continues to commit on
the tag hierarchy.
--
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
