You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Alex B (JIRA)" <ji...@codehaus.org> on 2008/03/25 16:50:58 UTC
[jira] Created: (MRELEASE-335) release:branch commits changes to
tags/ directory
release:branch commits changes to tags/ directory
-------------------------------------------------
Key: MRELEASE-335
URL: http://jira.codehaus.org/browse/MRELEASE-335
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: scm
Affects Versions: 2.0-beta-7
Reporter: Alex B
It should be possible to create a branch from a tag using the release plugin without comitting changes to the tags/ directory in subversion.
If this cannot be automated, then perhaps it should be possible to set the versions and scm urls etc after making the copy from the tag to the branch manually....
--
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] Commented: (MRELEASE-335) release:branch commits changes to
tags/ directory
Posted by "Frédéric Camblor (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249522#action_249522 ]
Frédéric Camblor commented on MRELEASE-335:
-------------------------------------------
Problem with your workaround (-DsuppressCommitBeforeBranch=true -DremoteTagging=false) is we should manually update <version> and <scm> tags in branch poms.
For me, it is not a convenient workaround.
> release:branch commits changes to tags/ directory
> -------------------------------------------------
>
> Key: MRELEASE-335
> URL: http://jira.codehaus.org/browse/MRELEASE-335
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-7
> Reporter: Alex B
>
> It should be possible to create a branch from a tag using the release plugin without comitting changes to the tags/ directory in subversion.
> If this cannot be automated, then perhaps it should be possible to set the versions and scm urls etc after making the copy from the tag to the branch manually....
--
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] Commented: (MRELEASE-335) release:branch commits changes to
tags/ directory
Posted by "Frédéric Camblor (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249543#action_249543 ]
Frédéric Camblor commented on MRELEASE-335:
-------------------------------------------
This is strange .. I ran it in batch mode with the following arguments :
mvn --batch-mode org.apache.maven.plugins:maven-release-plugin:2.1:branch -DautoVersionSubmodules=true -DtagBase=http://mysvnrepo/tags/ -Dtag=1.0test -DupdateBranchVersions=true -DreleaseVersion=1.0test -DbranchBase=http://mysvnrepo/branches/ -DbranchName=1.0test-bugfixes -DsuppressCommitBeforeBranch=true -DremoteTagging=false
If you remove the "-DsuppressCommitBeforeBranch=true -DremoteTagging=false", your "next branch version" will take the -DreleaseVersion value.
> release:branch commits changes to tags/ directory
> -------------------------------------------------
>
> Key: MRELEASE-335
> URL: http://jira.codehaus.org/browse/MRELEASE-335
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-7
> Reporter: Alex B
>
> It should be possible to create a branch from a tag using the release plugin without comitting changes to the tags/ directory in subversion.
> If this cannot be automated, then perhaps it should be possible to set the versions and scm urls etc after making the copy from the tag to the branch manually....
--
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] Issue Comment Edited: (MRELEASE-335) release:branch commits
changes to tags/ directory
Posted by "Frédéric Camblor (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249543#action_249543 ]
Frédéric Camblor edited comment on MRELEASE-335 at 12/23/10 4:08 AM:
---------------------------------------------------------------------
This is strange .. I ran it in batch mode with the following arguments :
mvn --batch-mode org.apache.maven.plugins:maven-release-plugin:2.1:branch -DautoVersionSubmodules=true -DtagBase=http://mysvnrepo/tags/ -Dtag=1.0test -DupdateBranchVersions=true -DreleaseVersion=1.0test-bugfixes -DbranchBase=http://mysvnrepo/branches/ -DbranchName=1.0test-bugfixes -DsuppressCommitBeforeBranch=true -DremoteTagging=false
If you remove the "-DsuppressCommitBeforeBranch=true -DremoteTagging=false", your "next branch version" will take the -DreleaseVersion value.
was (Author: fcamblor):
This is strange .. I ran it in batch mode with the following arguments :
mvn --batch-mode org.apache.maven.plugins:maven-release-plugin:2.1:branch -DautoVersionSubmodules=true -DtagBase=http://mysvnrepo/tags/ -Dtag=1.0test -DupdateBranchVersions=true -DreleaseVersion=1.0test -DbranchBase=http://mysvnrepo/branches/ -DbranchName=1.0test-bugfixes -DsuppressCommitBeforeBranch=true -DremoteTagging=false
If you remove the "-DsuppressCommitBeforeBranch=true -DremoteTagging=false", your "next branch version" will take the -DreleaseVersion value.
> release:branch commits changes to tags/ directory
> -------------------------------------------------
>
> Key: MRELEASE-335
> URL: http://jira.codehaus.org/browse/MRELEASE-335
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-7
> Reporter: Alex B
>
> It should be possible to create a branch from a tag using the release plugin without comitting changes to the tags/ directory in subversion.
> If this cannot be automated, then perhaps it should be possible to set the versions and scm urls etc after making the copy from the tag to the branch manually....
--
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] Commented: (MRELEASE-335) release:branch commits changes to
tags/ directory
Posted by "Marcin Kuthan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249540#action_249540 ]
Marcin Kuthan commented on MRELEASE-335:
----------------------------------------
Hi Frederic
I just check again my repository and <version> and <scm> were updated in the branch pom. You can find an example there:
http://code.google.com/p/m4enterprise/source/browse/branches/1.0.x/pom.xml?r=777
The only disadvantage is that I have to execute release:branch in interactive mode. I didn't find a solution how to pass the next branch version as a property.
> release:branch commits changes to tags/ directory
> -------------------------------------------------
>
> Key: MRELEASE-335
> URL: http://jira.codehaus.org/browse/MRELEASE-335
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-7
> Reporter: Alex B
>
> It should be possible to create a branch from a tag using the release plugin without comitting changes to the tags/ directory in subversion.
> If this cannot be automated, then perhaps it should be possible to set the versions and scm urls etc after making the copy from the tag to the branch manually....
--
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] Commented: (MRELEASE-335) release:branch commits changes to
tags/ directory
Posted by "Reinhard Nägele (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=195679#action_195679 ]
Reinhard Nägele commented on MRELEASE-335:
------------------------------------------
@Wim: I would have expected so, too, but even if {{updateWorkingCopyVersions}} is set to {{false}}, the working copy is committed (twice, actually, once with the changes for the branch, and once to revert those changes).
> release:branch commits changes to tags/ directory
> -------------------------------------------------
>
> Key: MRELEASE-335
> URL: http://jira.codehaus.org/browse/MRELEASE-335
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-7
> Reporter: Alex B
>
> It should be possible to create a branch from a tag using the release plugin without comitting changes to the tags/ directory in subversion.
> If this cannot be automated, then perhaps it should be possible to set the versions and scm urls etc after making the copy from the tag to the branch manually....
--
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] Commented: (MRELEASE-335) release:branch commits changes to
tags/ directory
Posted by "Wim Deblauwe (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162953#action_162953 ]
Wim Deblauwe commented on MRELEASE-335:
---------------------------------------
Isn't this already possible with {{-DupdateWorkingCopyVersions=false}} as stated in the [documentation|http://maven.apache.org/plugins/maven-release-plugin/examples/branch.html]?
> release:branch commits changes to tags/ directory
> -------------------------------------------------
>
> Key: MRELEASE-335
> URL: http://jira.codehaus.org/browse/MRELEASE-335
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-7
> Reporter: Alex B
>
> It should be possible to create a branch from a tag using the release plugin without comitting changes to the tags/ directory in subversion.
> If this cannot be automated, then perhaps it should be possible to set the versions and scm urls etc after making the copy from the tag to the branch manually....
--
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] Commented: (MRELEASE-335) release:branch commits changes to
tags/ directory
Posted by "Marcin Kuthan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249515#action_249515 ]
Marcin Kuthan commented on MRELEASE-335:
----------------------------------------
To avoid commits into tag, you can use the following command:
mvn release:branch -DbranchName=1.0.x -DupdateBranchVersions=true -DupdateWorkingCopyVersions=false -DsuppressCommitBeforeBranch=true -DremoteTagging=false
For me it should be a default behavior for release:branch. In my case the current development is made in trunk, released versions are tagged. If I need to fix released version, I create "patch" branch from the corresponding tag. E.g brach 1.0.x from tag 1.0. Make a fix and release 1.0.x branch as 1.0.1 (and the tag 1.0.1 is created as a result).
So, branch is always created from a tag not from a trunk. And according to the SVN book, created tag must not be changed.
> release:branch commits changes to tags/ directory
> -------------------------------------------------
>
> Key: MRELEASE-335
> URL: http://jira.codehaus.org/browse/MRELEASE-335
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-7
> Reporter: Alex B
>
> It should be possible to create a branch from a tag using the release plugin without comitting changes to the tags/ directory in subversion.
> If this cannot be automated, then perhaps it should be possible to set the versions and scm urls etc after making the copy from the tag to the branch manually....
--
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