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

["James Carman (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MRELEASE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=182753#action_182753 ] 

James Carman commented on MRELEASE-458:
---------------------------------------

I was using 2.0-beta-7:

          <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-release-plugin</artifactId>
                <version>2.0-beta-7</version>
                <configuration>
                    <preparationGoals>clean install</preparationGoals>
                    <autoVersionSubmodules>true</autoVersionSubmodules>
                </configuration>
            </plugin>

It seems like it stopped working correctly when I upgraded from Maven 2.0.x to Maven 2.1, if that helps any.

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