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/05/29 12:40:43 UTC
[jira] Created: (MRELEASE-123) release plugin does not take
commandline parameters into account
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
[jira] Commented: (MRELEASE-123) release plugin does not take
commandline parameters into account
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MRELEASE-123) release plugin does not take
commandline parameters into account
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-123?page=comments#action_66064 ]
Olivier Lamy commented on MRELEASE-123:
---------------------------------------
try with
-Darguments="-N"
--
Olivier
> 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
[jira] Issue Comment Edited: (MRELEASE-123) release plugin does not
take commandline parameters into account
Posted by "Stephen Connolly (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MRELEASE-123) release plugin does not take
commandline parameters into account
Posted by "Feniks Nator (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-123?page=comments#action_66063 ]
Feniks Nator commented on MRELEASE-123:
---------------------------------------
I'm having the same kind of problem here.
I want to do a release using the special settings.xml (because we let continuum build the artifact) file so I ran:
mvn release:perform -e -s %MAVEN_HOME%\conf\settings_continuum.xml -DconnectionUrl=...
As part of the release perform maven launches also the following:
[INFO] Executing: mvn deploy site-deploy --no-plugin-updates -P continuum,defaultprofile,continuum -DperformRelease=true
WITHOUT taking the original command-line arguments into account (which is a rather unexpected behavior, I find)
> 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
[jira] Updated: (MRELEASE-123) release plugin does not take
commandline parameters into account
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-123:
-------------------------------------
Component/s: prepare
> 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
> 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.
-
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
[jira] Commented: (MRELEASE-123) release plugin does not take
commandline parameters into account
Posted by "Grzegorz Slowikowski (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-123?page=comments#action_66066 ]
Grzegorz Slowikowski commented on MRELEASE-123:
-----------------------------------------------
Hi
I had the same problem.
-Darguments helps, but I think it's for non-standard parameters, eg.
-Darguments="-Dmaven.test.skip=true", which are not on mvn release:prepare
command line.
I don't know which ones, but -N should definitely be copied to invoked command line
because it means that I don't want subprojects to be released so nothing should
be done to them.
Greg
> 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
[jira] Commented: (MRELEASE-123) release plugin does not take
commandline parameters into account
Posted by "Stephen Connolly (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272033#comment-272033 ]
Stephen Connolly commented on MRELEASE-123:
-------------------------------------------
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
[jira] Commented: (MRELEASE-123) release plugin does not take
commandline parameters into account
Posted by "Jorg Heymans (JIRA)" <ji...@codehaus.org>.
[ 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