You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2010/01/31 04:15:56 UTC

[jira] Updated: (MRELEASE-458) Branch Does Not Honor updateWorkingCopyVersions Setting

     [ http://jira.codehaus.org/browse/MRELEASE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MRELEASE-458:
----------------------------------

    Affects Version/s: 2.0-beta-7
                       2.0-beta-9
        Fix Version/s: 2.0.1

> 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.0.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