[
http://jira.codehaus.org/browse/MRELEASE-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115300
]
Santhosh Kumar commented on MRELEASE-173:
-----------------------------------------
Adding these two command line parameters greatly simplifies the integration of
maven into the automated build tools. I would assume these two parameters
behave this way.
1. If releaseVersion is specified, it would override the current pom.xml
version. If running in interactive mode, this version would be used as default
answer.
2. If devVersion is specified, "-SNAPSHOT" would be suffixed and used as new
dev version. If running in interactive mode, it would be used as default
answer. If devVersion is not specified, then version computed from step 1 would
be incremented by one (with -SNAPSHOT) and used.
We have modified the release plugin 2.4-alpha4 version in our internal
environment to have this feature. I can post the diff file if it helps.
> 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
