You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephen Connolly (JIRA)" <ji...@codehaus.org> on 2011/07/01 13:53:42 UTC
[jira] Issue Comment Edited: (MRELEASE-123) release plugin does not
take commandline parameters into account
[ https://jira.codehaus.org/browse/MRELEASE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272033#comment-272033 ]
Stephen Connolly edited comment on MRELEASE-123 at 7/1/11 6:52 AM:
-------------------------------------------------------------------
One could also argue that with Maven 3.0.x's reactor mode any -pl should be passed through also. In which case the desire is to release the {{$\{reactorProjects}}}... that might make the fix for 3.0.x+ easier but not sure how you'd implement for 2.x
was (Author: stephenconnolly):
One could also argue that with Maven 3.0.x's reactor mode any -pl should be passed through also
> release plugin does not take commandline parameters into account
> ----------------------------------------------------------------
>
> Key: MRELEASE-123
> URL: https://jira.codehaus.org/browse/MRELEASE-123
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira