You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jorg Heymans (JIRA)" <ji...@codehaus.org> on 2006/06/08 21:00:43 UTC
[jira] Commented: (MRELEASE-123) release plugin does not take
commandline parameters into account
[ http://jira.codehaus.org/browse/MRELEASE-123?page=comments#action_66966 ]
Jorg Heymans commented on MRELEASE-123:
---------------------------------------
toying around with this, it seems that
mvn release:prepare -N -Darguments=-N
does seem to work for releasing a top-level pom only. It's a bit counter-intuitive at first but makes sense when you think about it. The first -N kicks in at the command line directly and the second one when the integration run is forked.
> release plugin does not take commandline parameters into account
> ----------------------------------------------------------------
>
> Key: MRELEASE-123
> URL: http://jira.codehaus.org/browse/MRELEASE-123
> Project: Maven 2.x Release Plugin
> Type: Bug
> Versions: 2.0-beta-4
> Reporter: Jorg Heymans
>
>
> i would like to do a release of a top-level pom only : intuitively i do "mvn -N release:prepare". During release preparation the -N parameter is left out however and maven does a full integration on all child modules and subsequently includes them in the release process.
--
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