[MRELEASE-173] Allow command line specification of versions

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-beta-3, 2.0-beta-4, 2.0-beta-5
• Fix Version/s: 2.0-beta-8
• Flags: Patch
• Assignee: Paul Gier
• Reporter: Chris Tucker
• Created: 06/Nov/06 16:44
• Updated: 05/Apr/15 14:53
• Resolved: 13/May/08 16:27

Description

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.

Issue Links

• is duplicated by: MRELEASE-321 Add support for -DdevelopmentVersion and -DreleaseVersion to facilitate command line configuration
• is related to: MRELEASE-387 command line versions don't seem to work on release:branch
• is related to: MRELEASE-100 implement release:release goal
• relates to: MRELEASE-389 Properties releaseVersion and developmentVersion are not read correctly during release:prepare (eventually release:perform)