maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Janes (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MRELEASE-458) Branch Does Not Honor updateWorkingCopyVersions Setting
Date Mon, 01 Feb 2010 14:34:55 GMT

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

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

updateWorkingCopyVersions=false appears to work again in the 2.0 release candidate (currently
under vote), although there's a caveat: the POM in the source branch or tag is checked in
twice during the branch, once to change the version to match the branch and once to change
it back.  This means that a (theoretically unchanging) tag is modified, although it's immediately
undone.

For what it's worth, the behaviour is the same regardless of the setting of the remoteTagging
property.

Checked on Maven 2.2.1 on Linux with Subversion 1.6.6 using the staged repository and this
command line:

{{mvn org.apache.maven.plugins:maven-release-plugin:2.0:branch -Pstage-release -DbranchName=test-1.0.x
-DupdateBranchVersions=true -DupdateWorkingCopyVersions=false}}

> 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

        

Mime
View raw message