You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Gier (JIRA)" <ji...@codehaus.org> on 2008/04/23 04:13:55 UTC

[jira] Commented: (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=131811#action_131811 ] 

Paul Gier commented on MRELEASE-173:
------------------------------------

I took a different approach than what was in the patch, since the patch was out of date and only handled single version releases.  To set the release version from the command line, you now have to use project.rel or project.dev and the groupId and artifactId.  So you end up with something like this:

mvn --batch-mode -Dtag=my-proj-1.2 -Dproject.rel.org.myCompany:projectA=1.2 \
     -Dproject.dev.org.myCompany:projectA=1.3-SNAPSHOT release:prepare

This allows multiple versions to be passed for a multi-module release.  There is now an example for this in the site docs in svn.


> 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