You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Elias Ross (JIRA)" <ji...@codehaus.org> on 2008/04/23 05:31:56 UTC
[jira] Issue Comment Edited: (MRELEASE-173) Allow command line
specification of versions
[ http://jira.codehaus.org/browse/MRELEASE-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131818#action_131818 ]
genman edited comment on MRELEASE-173 at 4/22/08 10:30 PM:
---------------------------------------------------------------
Requiring groupId and artifactId for the use case of single version releases just complicates writing scripts and using build tools. I'm against what Paul suggests, or at least I'm for a single-version solution.
And honestly, I never understood the use case of releasing multiple artifacts with different versions, which just sounds like it would cause trouble. Have you seen any automated build tools that would simultaneously build a single project with N different sub versions?
was (Author: genman):
Requiring groupId and artifactId for the use case of single version releases just complicates writing scripts and using build tools. I'm against what Paul suggests, or at least I'm for a single-version solution.
And honestly, I never understood the use case of releasing multiple artifacts with different versions, which just sounds like it would cause trouble. Have you seen any build tools that would support building a project with N different sub versions?
There's now 17 votes for this trivial feature and so I wonder why nobody's taken it on...
> Allow command line specification of versions
> --------------------------------------------
>
> Key: MRELEASE-173
> URL: http://jira.codehaus.org/browse/MRELEASE-173
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Affects Versions: 2.0-beta-3, 2.0-beta-4, 2.0-beta-5
> Reporter: Chris Tucker
> Assignee: Paul Gier
> Fix For: 2.0-beta-8
>
> Attachments: release-version.diff
>
>
> It is convenient in a batchMode environment to specify the version to release and the new version to update SNAPSHOT artifacts to. The attached patch against maven-release-manager and maven-release-plugin provides the basic functionality to allow this.
> The maven-release-plugin will now accept two new arguments:
> -DreleaseVersion=<version string for release>
> -DdevVersion=<version string for next development cycle>
> For example, to release version 1.2 of a project and move up to version 2.0-SNAPSHOT one would issue:
> $ mvn release:clean release:prepare -DreleaseVersion=1.2 -DdevVersion=2.0 --batch-mode
> This patch is against current trunk (471862). It currently doesn't support resuming, so a release:clean is necessary if a previous release attempt has been prepared.
--
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