[
http://jira.codehaus.org/browse/MRELEASE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249543#action_249543
]
Frédéric Camblor commented on MRELEASE-335:
-------------------------------------------
This is strange .. I ran it in batch mode with the following arguments :
mvn --batch-mode org.apache.maven.plugins:maven-release-plugin:2.1:branch
-DautoVersionSubmodules=true -DtagBase=http://mysvnrepo/tags/ -Dtag=1.0test
-DupdateBranchVersions=true -DreleaseVersion=1.0test
-DbranchBase=http://mysvnrepo/branches/ -DbranchName=1.0test-bugfixes
-DsuppressCommitBeforeBranch=true -DremoteTagging=false
If you remove the "-DsuppressCommitBeforeBranch=true -DremoteTagging=false",
your "next branch version" will take the -DreleaseVersion value.
> release:branch commits changes to tags/ directory
> -------------------------------------------------
>
> Key: MRELEASE-335
> URL: http://jira.codehaus.org/browse/MRELEASE-335
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-7
> Reporter: Alex B
>
> It should be possible to create a branch from a tag using the release plugin
> without comitting changes to the tags/ directory in subversion.
> If this cannot be automated, then perhaps it should be possible to set the
> versions and scm urls etc after making the copy from the tag to the branch
> manually....
--
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
