You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lars Corneliussen (JIRA)" <ji...@codehaus.org> on 2010/08/09 12:46:32 UTC

[jira] Created: (MRELEASE-585) release:branch commits working copy changes even when -DupdateWorkingCopyVersions=false

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

        

[jira] Closed: (MRELEASE-585) release:branch commits working copy changes even when -DupdateWorkingCopyVersions=false

Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRELEASE-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Lundberg closed MRELEASE-585.
------------------------------------

    Resolution: 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

        

[jira] Commented: (MRELEASE-585) release:branch commits working copy changes even when -DupdateWorkingCopyVersions=false

Posted by "Lars Corneliussen (JIRA)" <ji...@codehaus.org>.
    [ 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