You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dan Fabulich (JIRA)" <ji...@codehaus.org> on 2008/02/23 23:40:28 UTC
[jira] Created: (MRELEASE-324) There should be a way to update POM
version numbers without tagging/branching
There should be a way to update POM version numbers without tagging/branching
-----------------------------------------------------------------------------
Key: MRELEASE-324
URL: http://jira.codehaus.org/browse/MRELEASE-324
Project: Maven 2.x Release Plugin
Issue Type: Improvement
Reporter: Dan Fabulich
Updating versions is useful; sometimes you just want to change the version numbers in your POMs without checking in right away. There should be a way to do that. It could either be a new goal (release:update-versions) or simply an option on release:prepare to avoid tagging.
Why would you want this?
... because you need to use svnmerge.py http://www.orcaware.com/svn/wiki/Svnmerge.py
... because you're using an unsupported SCM MRELEASE-184
... because you need to take other manual steps before tagging (updating other metadata files)
... because you need to make a branch instead of making a tag MRELEASE-203
... because you're skipping version numbers (I was calling this 1.1-SNAPSHOT, but now I want to call it 2.0-SNAPSHOT)
... because you don't want to tag until after you've blessed the release (in the Maven release process, if the vote fails, you have to delete the tag)
... because you want to update your version number to contain special build-based metadata every time you build
--
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] Updated: (MRELEASE-324) There should be a way to update POM
version numbers without tagging/branching
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-324:
-------------------------------------
Component/s: prepare
> There should be a way to update POM version numbers without tagging/branching
> -----------------------------------------------------------------------------
>
> Key: MRELEASE-324
> URL: http://jira.codehaus.org/browse/MRELEASE-324
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
> Reporter: Dan Fabulich
>
> Updating versions is useful; sometimes you just want to change the version numbers in your POMs without checking in right away. There should be a way to do that. It could either be a new goal (release:update-versions) or simply an option on release:prepare to avoid tagging.
> Why would you want this?
> ... because you need to use svnmerge.py http://www.orcaware.com/svn/wiki/Svnmerge.py
> ... because you're using an unsupported SCM MRELEASE-184
> ... because you need to take other manual steps before tagging (updating other metadata files)
> ... because you need to make a branch instead of making a tag MRELEASE-203
> ... because you're skipping version numbers (I was calling this 1.1-SNAPSHOT, but now I want to call it 2.0-SNAPSHOT)
> ... because you don't want to tag until after you've blessed the release (in the Maven release process, if the vote fails, you have to delete the tag)
> ... because you want to update your version number to contain special build-based metadata every time you build
--
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] Updated: (MRELEASE-324) There should be a way to update POM
version numbers without tagging/branching
Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Gier updated MRELEASE-324:
-------------------------------
Fix Version/s: 2.0-beta-10
> There should be a way to update POM version numbers without tagging/branching
> -----------------------------------------------------------------------------
>
> Key: MRELEASE-324
> URL: http://jira.codehaus.org/browse/MRELEASE-324
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
> Reporter: Dan Fabulich
> Assignee: Paul Gier
> Fix For: 2.0-beta-10
>
>
> Updating versions is useful; sometimes you just want to change the version numbers in your POMs without checking in right away. There should be a way to do that. It could either be a new goal (release:update-versions) or simply an option on release:prepare to avoid tagging.
> Why would you want this?
> ... because you need to use svnmerge.py http://www.orcaware.com/svn/wiki/Svnmerge.py
> ... because you're using an unsupported SCM MRELEASE-184
> ... because you need to take other manual steps before tagging (updating other metadata files)
> ... because you need to make a branch instead of making a tag MRELEASE-203
> ... because you're skipping version numbers (I was calling this 1.1-SNAPSHOT, but now I want to call it 2.0-SNAPSHOT)
> ... because you don't want to tag until after you've blessed the release (in the Maven release process, if the vote fails, you have to delete the tag)
> ... because you want to update your version number to contain special build-based metadata every time you build
--
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-324) There should be a way to update
POM version numbers without tagging/branching
Posted by "Steve Ebersole (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181687#action_181687 ]
Steve Ebersole commented on MRELEASE-324:
-----------------------------------------
Also w/o doing a build (install).
> There should be a way to update POM version numbers without tagging/branching
> -----------------------------------------------------------------------------
>
> Key: MRELEASE-324
> URL: http://jira.codehaus.org/browse/MRELEASE-324
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
> Reporter: Dan Fabulich
>
> Updating versions is useful; sometimes you just want to change the version numbers in your POMs without checking in right away. There should be a way to do that. It could either be a new goal (release:update-versions) or simply an option on release:prepare to avoid tagging.
> Why would you want this?
> ... because you need to use svnmerge.py http://www.orcaware.com/svn/wiki/Svnmerge.py
> ... because you're using an unsupported SCM MRELEASE-184
> ... because you need to take other manual steps before tagging (updating other metadata files)
> ... because you need to make a branch instead of making a tag MRELEASE-203
> ... because you're skipping version numbers (I was calling this 1.1-SNAPSHOT, but now I want to call it 2.0-SNAPSHOT)
> ... because you don't want to tag until after you've blessed the release (in the Maven release process, if the vote fails, you have to delete the tag)
> ... because you want to update your version number to contain special build-based metadata every time you build
--
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-324) There should be a way to update
POM version numbers without tagging/branching
Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190898#action_190898 ]
Paul Gier commented on MRELEASE-324:
------------------------------------
Added a new goal called "update-versions" in [r814798|http://svn.apache.org/viewvc?view=rev&revision=814798].
> There should be a way to update POM version numbers without tagging/branching
> -----------------------------------------------------------------------------
>
> Key: MRELEASE-324
> URL: http://jira.codehaus.org/browse/MRELEASE-324
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
> Reporter: Dan Fabulich
> Assignee: Paul Gier
> Fix For: 2.0-beta-10
>
>
> Updating versions is useful; sometimes you just want to change the version numbers in your POMs without checking in right away. There should be a way to do that. It could either be a new goal (release:update-versions) or simply an option on release:prepare to avoid tagging.
> Why would you want this?
> ... because you need to use svnmerge.py http://www.orcaware.com/svn/wiki/Svnmerge.py
> ... because you're using an unsupported SCM MRELEASE-184
> ... because you need to take other manual steps before tagging (updating other metadata files)
> ... because you need to make a branch instead of making a tag MRELEASE-203
> ... because you're skipping version numbers (I was calling this 1.1-SNAPSHOT, but now I want to call it 2.0-SNAPSHOT)
> ... because you don't want to tag until after you've blessed the release (in the Maven release process, if the vote fails, you have to delete the tag)
> ... because you want to update your version number to contain special build-based metadata every time you build
--
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-324) There should be a way to update POM
version numbers without tagging/branching
Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Gier closed MRELEASE-324.
------------------------------
Resolution: Fixed
> There should be a way to update POM version numbers without tagging/branching
> -----------------------------------------------------------------------------
>
> Key: MRELEASE-324
> URL: http://jira.codehaus.org/browse/MRELEASE-324
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
> Reporter: Dan Fabulich
> Assignee: Paul Gier
> Fix For: 2.0-beta-10
>
>
> Updating versions is useful; sometimes you just want to change the version numbers in your POMs without checking in right away. There should be a way to do that. It could either be a new goal (release:update-versions) or simply an option on release:prepare to avoid tagging.
> Why would you want this?
> ... because you need to use svnmerge.py http://www.orcaware.com/svn/wiki/Svnmerge.py
> ... because you're using an unsupported SCM MRELEASE-184
> ... because you need to take other manual steps before tagging (updating other metadata files)
> ... because you need to make a branch instead of making a tag MRELEASE-203
> ... because you're skipping version numbers (I was calling this 1.1-SNAPSHOT, but now I want to call it 2.0-SNAPSHOT)
> ... because you don't want to tag until after you've blessed the release (in the Maven release process, if the vote fails, you have to delete the tag)
> ... because you want to update your version number to contain special build-based metadata every time you build
--
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