[
http://jira.codehaus.org/browse/MRELEASE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132806#action_132806
]
Benjamin Bentmann commented on MRELEASE-123:
--------------------------------------------
bq. but -N should definitely be copied to invoked command line
I fully agree. That the Release Plugin is forking a Maven build is an
implementation detail. A user shouldn't be bothered with pushing parameters
down to this forked Maven invocation. By putting -N on the command line he
stated his intention to perform a non-recursive build/release. What would be
the rationale to repeat this intention? Are there use cases where the recursive
flag would be different for the main build and the forked build?
> 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
> Issue Type: Bug
> Affects 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
