You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Peter Janes (JIRA)" <ji...@codehaus.org> on 2009/11/06 20:59:55 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 ]

Peter Janes updated MRELEASE-458:
---------------------------------

    Attachment: MRELEASE-458-test.diff

The attached file contains a (failing) test case for "mvn release:branch -DupdateWorkingCopyVersions=false".  With luck it will help someone verify a fix.

(The patch moves much of the configuration for the existing ITs into a separate execution as the current tests are limited to testing release:prepare.)

> 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
>            Reporter: James Carman
>         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