[jira] Commented: (MRELEASE-335) release:branch commits changes to tags/ directory

["Marcin Kuthan (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MRELEASE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249515#action_249515 ] 

Marcin Kuthan commented on MRELEASE-335:
----------------------------------------

To avoid commits into tag, you can use the following command:
mvn release:branch  -DbranchName=1.0.x -DupdateBranchVersions=true -DupdateWorkingCopyVersions=false -DsuppressCommitBeforeBranch=true -DremoteTagging=false

For me it should be a default behavior for release:branch. In my case the current development is made in trunk, released versions are tagged. If I need to fix released version, I create "patch" branch from the corresponding tag. E.g brach 1.0.x from tag 1.0. Make a fix and release 1.0.x branch as 1.0.1 (and the tag 1.0.1 is created as a result). 

So, branch is always created from a tag not from a trunk. And according to the SVN book, created tag must not be changed.



> 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