[
http://jira.codehaus.org/browse/MRELEASE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=219988#action_219988
]
Lars Corneliussen commented on MRELEASE-458:
--------------------------------------------
There is only two possibilities to solve this.
# Create a branch, switch to it (or do a checkout somewhere) and then change
the versions
# Only use together with remoteTagging=false
For the latter I have a patch (for 2.0) locally that works fine. In the
ScmCommitPhase i first validate that for branches, !updateWorkingCopyVersions
always is used in conjunction with !remoteTagging.
In execute I skip the commit for branches when both flags are false. If this is
suitable and likely to make it into a future release, I'm happy to write some
tests and submit it, too.
> Branch Does Not Honor updateWorkingCopyVersions Setting
> -------------------------------------------------------
>
> Key: MRELEASE-458
> URL: http://jira.codehaus.org/browse/MRELEASE-458
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.0-beta-7, 2.0-beta-9
> Reporter: James Carman
> Fix For: 2.1
>
> Attachments: MRELEASE-458-test.diff
>
>
> I copied the following command line from the documentation site
> (http://maven.apache.org/plugins/maven-release-plugin/examples/branch.html):
> mvn release:branch -DbranchName=my-branch -DupdateBranchVersions=true
> -DupdateWorkingCopyVersions=false
> I have used this method in the past to cut a milestone release from our
> trunk. However, it seems that the working copy is actually being modified
> now. Has there been a newer release or something?
--
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
