[
http://jira.codehaus.org/browse/MRELEASE-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111083
]
Marc-Andre Houle commented on MRELEASE-173:
-------------------------------------------
I would really appreciate this feature. For many building system, that can be
very neat because you don't always have the possibility to enter the version
number.
Does the developpers need some help or whatever? Since I need it, I'm ready to
try helping implementing this feature to include it in next releases. Is
there lot of thing missing than this diff file?
Marc
> 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
> 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
