[ 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
