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/25 00:29:46 UTC
[jira] Closed: (MRELEASE-321) Add support for -DdevelopmentVersion
and -DreleaseVersion to facilitate command line configuration
[ http://jira.codehaus.org/browse/MRELEASE-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Gier closed MRELEASE-321.
------------------------------
Resolution: Duplicate
I believe this issue has been fixed in MRELEASE-173
> Add support for -DdevelopmentVersion and -DreleaseVersion to facilitate command line configuration
> --------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-321
> URL: http://jira.codehaus.org/browse/MRELEASE-321
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Affects Versions: 2.0-beta-7
> Reporter: Christian Nelson
> Fix For: 2.0-beta-8
>
>
> We're about to start using the maven-release-plugin on a large project for both branching and releasing. We found a few things that would be nice to pass in as arguments on the command line so that the process doesn't require user interaction. I looked to see if this was already possible and came up blank.
> *Scenario 1*: release:branch needs two pieces of information: (a) the branch name and (b) the "new working copy version". The former can be specified using -DbranchName but the latter isn't documented. Is there a way to specify the new working copy version on the command line? Ideally I'd be able to do something like this:
> | $ mvn release:branch -DbranchName=release-3.1 -DdevelopmentVersion= 3.2-SNAPSHOT
> *Scenario 2*: release:prepare needs three pieces of information: (a) the release version, (b) the release scm tag, and (c) the new development version. According to the documentation, only the tag can be specified on the command line using -Dtag=wombat. What about the others?
> | $ mvn release:prepare -DreleaseVersion=3.1 -Dtag=release-3.1.0-DdevelopmentVersion=3.1.1-SNAPSHOT
> Note we're also using -DautoVersionSubmodules=true, which is what gets us pretty far in being able to fire these things off in a single shot without user interaction.
> I've been meaning to code up a fix so that I can submit it with this issue, but haven't had the time yet. I hope to find the time soon, but in the mean time would like some feedback on the idea (e.g. is there a way to do it already?).
--
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