[
http://jira.codehaus.org/browse/MRELEASE-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231447#action_231447
]
Lars Corneliussen commented on MRELEASE-585:
--------------------------------------------
ups... I mixed up "fixed" versions with "resolved".... so MRELEASE-458 is
fine... I'll add the patch there.
This issue can be closed as duplicate.
> release:branch commits working copy changes even when
> -DupdateWorkingCopyVersions=false
> ---------------------------------------------------------------------------------------
>
> Key: MRELEASE-585
> URL: http://jira.codehaus.org/browse/MRELEASE-585
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.0
> Reporter: Lars Corneliussen
>
> MRELEASE-471 and MRELEASE-458 already described the problem.
> The fixes made were only workarounds. Branch now commits the changes, then
> performs the release, and then it rolles back the changes made to the working
> copy.
> For SVN, if remoteTagging is false, it could create the branch from the
> workingcopy before checking it in.
> I'm working on a patch that I will submit soon.
--
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
