maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Gier (JIRA)" <>
Subject [jira] Closed: (MRELEASE-173) Allow command line specification of versions
Date Tue, 13 May 2008 21:28:28 GMT


Paul Gier closed MRELEASE-173.

    Resolution: Fixed

> Allow command line specification of versions
> --------------------------------------------
>                 Key: MRELEASE-173
>                 URL:
>             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:
For more information on JIRA, see:


View raw message