You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benson Margulies (JIRA)" <ji...@codehaus.org> on 2010/03/25 16:39:23 UTC
[jira] Created: (MRELEASE-535) release:branch poked trunk poms
release:branch poked trunk poms
-------------------------------
Key: MRELEASE-535
URL: http://jira.codehaus.org/browse/MRELEASE-535
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: branch
Affects Versions: 2.0
Reporter: Benson Margulies
I ran the following:
mvn org.apache.maven.plugins:maven-release-plugin:2.0:branch -Prelease -DbranchName=segmentation -DupdateBranchVersions=true -DupdateWorkingCopyVersions=false
It failed. However, before it failed, it checked new poms into the trunk that had the scm and version info for the branch.
What I expected it to do was (1) create the branch, and (2) edit the poms *in the branch*, leaving the trunk untouched.
Further, release:rollback failed with an NPE when I ran it after the failure to try to unwind this mess.
--
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] Closed: (MRELEASE-535) release:branch poked trunk poms
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benson Margulies closed MRELEASE-535.
-------------------------------------
Resolution: Not A Bug
THis was just stupid.
> release:branch poked trunk poms
> -------------------------------
>
> Key: MRELEASE-535
> URL: http://jira.codehaus.org/browse/MRELEASE-535
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.0
> Reporter: Benson Margulies
>
> I ran the following:
> mvn org.apache.maven.plugins:maven-release-plugin:2.0:branch -Prelease -DbranchName=segmentation -DupdateBranchVersions=true -DupdateWorkingCopyVersions=false
> It failed. However, before it failed, it checked new poms into the trunk that had the scm and version info for the branch.
> What I expected it to do was (1) create the branch, and (2) edit the poms *in the branch*, leaving the trunk untouched.
> Further, release:rollback failed with an NPE when I ran it after the failure to try to unwind this mess.
--
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