Created: (MRELEASE-458) Branch Does Not Honor updateWorkingCopyVersions Setting

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

       

    [ 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

       

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

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

I verified it.  This seems to be working correctly on my work machine.  It's running fedora linux 9 64-bit with maven 2.0.9.  The machine that it fails on is a Microsoft Vista Business 32-bit with maven 2.1.0.  They're are both now using the 2.0-beta-7 version of the release plugin.  Hope that helps.  

> 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

       

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

Peter Janes commented on MRELEASE-458:
--------------------------------------

It's also present in 2.0-beta-9 running under Maven 2.2.1 (Fedora 11 64-bit).

> 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

       

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

Klaus Wienert commented on MRELEASE-458:
----------------------------------------

I could approve it with maven-release-plugin:2.0-beta-9 using Maven 2.0.10.

    <pluginManagement>
      <plugins>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-release-plugin</artifactId>
          <version>2.0-beta-9</version>
        </plugin>
      </plugins>
    </pluginManagement>

path>mvn -version
Maven version: 2.0.10
Java version: 1.6.0_03
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
path>cd target\checkout

path\target\checkout>mvn release:branch -DbranchName=k2006-1.5.8-patch1 -DupdateBranchVersions=true -DupdateWorkingCopyVersions=false
-DdryRun=true
[INFO] Scanning for projects...
[INFO] Reactor build order:
...
[INFO] Full run would be checking in 9 files with message: '[maven-release-plugin] prepare branch k2006-1.5.8-patch1'
[INFO] Full run would be branching path\target\checkout with label: 'k2006-1.5.8-patch1'
...
[INFO] Full run would be checking in 9 files with message: '[maven-release-plugin] prepare release k2006-1.5.8-patch1'
[INFO] Release preparation simulation complete.
[INFO] Cleaning up after release...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8 seconds
[INFO] Finished at: Wed Oct 07 11:13:49 CEST 2009
[INFO] Final Memory: 8M/16M
[INFO] ------------------------------------------------------------------------
path\target\checkout>

> 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

       

     [ 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