[
https://jira.codehaus.org/browse/MRELEASE-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=300215#comment-300215
]
Scott Carey commented on MRELEASE-635:
--------------------------------------
Yes, I probably meant prepare.
I have since decided against using maven-release due to the conflation of
version management and branching. versions-maven-plugin "does one thing and
does it well", and can be composed with SCM tools to achieve similar objectives
with more flexibility.
> perform does not honor updateWorkingCopiesVersion setting
> ---------------------------------------------------------
>
> Key: MRELEASE-635
> URL: https://jira.codehaus.org/browse/MRELEASE-635
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.1
> Reporter: Scott Carey
>
> release:perform modifies the working copies version when configured not to.
> This was a tag directly from trunk.
> <configuration>
> <autoVersionSubmodules>true</autoVersionSubmodules>
> <remoteTagging>false</remoteTagging>
> <suppressCommitBeforeTag>true</suppressCommitBeforeTag>
> <suppressCommitBeforeBranch>true</suppressCommitBeforeBranch>
> <updateBranchVersions>true</updateBranchVersions>
> <updateWorkingCopyVersions>false</updateWorkingCopyVersions>
> </configuration>
> Happens in both dryRun mode and normal.
> After a non-dryRun pom.xml.releaseBackup files are left behind as well.
> The desired behavior is to leave the working copy alone and only modify the
> tag. Currently, with suppressCommitBeforeTag true, this is possible by
> reverting the local changes left behind by running release:perform.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
