You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Scott Carey (JIRA)" <ji...@codehaus.org> on 2011/01/20 08:05:57 UTC
[jira] Created: (MRELEASE-635) perform does not honor
updateWorkingCopiesVersion setting
perform does not honor updateWorkingCopiesVersion setting
---------------------------------------------------------
Key: MRELEASE-635
URL: http://jira.codehaus.org/browse/MRELEASE-635
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: perform
Affects Versions: 2.1
Reporter: Scott Carey
release:perform modifies the working copies version when configured not to. This was a tag directly from trunk.
<configuration>
<autoVersionSubmodules>true</autoVersionSubmodules>
<remoteTagging>false</remoteTagging>
<suppressCommitBeforeTag>true</suppressCommitBeforeTag>
<suppressCommitBeforeBranch>true</suppressCommitBeforeBranch>
<updateBranchVersions>true</updateBranchVersions>
<updateWorkingCopyVersions>false</updateWorkingCopyVersions>
</configuration>
Happens in both dryRun mode and normal.
After a non-dryRun pom.xml.releaseBackup files are left behind as well.
The desired behavior is to leave the working copy alone and only modify the tag. Currently, with suppressCommitBeforeTag true, this is possible by reverting the local changes left behind by running release:perform.
--
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
[jira] (MRELEASE-635) perform does not honor
updateWorkingCopiesVersion setting
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-635.
-----------------------------------
Resolution: Duplicate
Assignee: Robert Scholte
Superseded by MRELEASE-760, which will be part of the next release.
> perform does not honor updateWorkingCopiesVersion setting
> ---------------------------------------------------------
>
> Key: MRELEASE-635
> URL: https://jira.codehaus.org/browse/MRELEASE-635
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.1
> Reporter: Scott Carey
> Assignee: Robert Scholte
>
> release:perform modifies the working copies version when configured not to. This was a tag directly from trunk.
> <configuration>
> <autoVersionSubmodules>true</autoVersionSubmodules>
> <remoteTagging>false</remoteTagging>
> <suppressCommitBeforeTag>true</suppressCommitBeforeTag>
> <suppressCommitBeforeBranch>true</suppressCommitBeforeBranch>
> <updateBranchVersions>true</updateBranchVersions>
> <updateWorkingCopyVersions>false</updateWorkingCopyVersions>
> </configuration>
> Happens in both dryRun mode and normal.
> After a non-dryRun pom.xml.releaseBackup files are left behind as well.
> The desired behavior is to leave the working copy alone and only modify the tag. Currently, with suppressCommitBeforeTag true, this is possible by reverting the local changes left behind by running release:perform.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-635) perform does not honor
updateWorkingCopiesVersion setting
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte updated MRELEASE-635:
------------------------------------
Component/s: (was: perform)
prepare
> perform does not honor updateWorkingCopiesVersion setting
> ---------------------------------------------------------
>
> Key: MRELEASE-635
> URL: https://jira.codehaus.org/browse/MRELEASE-635
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.1
> Reporter: Scott Carey
>
> release:perform modifies the working copies version when configured not to. This was a tag directly from trunk.
> <configuration>
> <autoVersionSubmodules>true</autoVersionSubmodules>
> <remoteTagging>false</remoteTagging>
> <suppressCommitBeforeTag>true</suppressCommitBeforeTag>
> <suppressCommitBeforeBranch>true</suppressCommitBeforeBranch>
> <updateBranchVersions>true</updateBranchVersions>
> <updateWorkingCopyVersions>false</updateWorkingCopyVersions>
> </configuration>
> Happens in both dryRun mode and normal.
> After a non-dryRun pom.xml.releaseBackup files are left behind as well.
> The desired behavior is to leave the working copy alone and only modify the tag. Currently, with suppressCommitBeforeTag true, this is possible by reverting the local changes left behind by running release:perform.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-635) perform does not honor
updateWorkingCopiesVersion setting
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=300145#comment-300145 ]
Robert Scholte commented on MRELEASE-635:
-----------------------------------------
I guess you meant {{release:prepare}}, right?
> perform does not honor updateWorkingCopiesVersion setting
> ---------------------------------------------------------
>
> Key: MRELEASE-635
> URL: https://jira.codehaus.org/browse/MRELEASE-635
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.1
> Reporter: Scott Carey
>
> release:perform modifies the working copies version when configured not to. This was a tag directly from trunk.
> <configuration>
> <autoVersionSubmodules>true</autoVersionSubmodules>
> <remoteTagging>false</remoteTagging>
> <suppressCommitBeforeTag>true</suppressCommitBeforeTag>
> <suppressCommitBeforeBranch>true</suppressCommitBeforeBranch>
> <updateBranchVersions>true</updateBranchVersions>
> <updateWorkingCopyVersions>false</updateWorkingCopyVersions>
> </configuration>
> Happens in both dryRun mode and normal.
> After a non-dryRun pom.xml.releaseBackup files are left behind as well.
> The desired behavior is to leave the working copy alone and only modify the tag. Currently, with suppressCommitBeforeTag true, this is possible by reverting the local changes left behind by running release:perform.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-635) perform does not honor
updateWorkingCopiesVersion setting
Posted by "Scott Carey (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=300215#comment-300215 ]
Scott Carey commented on MRELEASE-635:
--------------------------------------
Yes, I probably meant prepare.
I have since decided against using maven-release due to the conflation of version management and branching. versions-maven-plugin "does one thing and does it well", and can be composed with SCM tools to achieve similar objectives with more flexibility.
> perform does not honor updateWorkingCopiesVersion setting
> ---------------------------------------------------------
>
> Key: MRELEASE-635
> URL: https://jira.codehaus.org/browse/MRELEASE-635
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.1
> Reporter: Scott Carey
>
> release:perform modifies the working copies version when configured not to. This was a tag directly from trunk.
> <configuration>
> <autoVersionSubmodules>true</autoVersionSubmodules>
> <remoteTagging>false</remoteTagging>
> <suppressCommitBeforeTag>true</suppressCommitBeforeTag>
> <suppressCommitBeforeBranch>true</suppressCommitBeforeBranch>
> <updateBranchVersions>true</updateBranchVersions>
> <updateWorkingCopyVersions>false</updateWorkingCopyVersions>
> </configuration>
> Happens in both dryRun mode and normal.
> After a non-dryRun pom.xml.releaseBackup files are left behind as well.
> The desired behavior is to leave the working copy alone and only modify the tag. Currently, with suppressCommitBeforeTag true, this is possible by reverting the local changes left behind by running release:perform.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira