[
https://jira.codehaus.org/browse/MRELEASE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283142#comment-283142
]
Derek Lewis commented on MRELEASE-577:
--------------------------------------
Using -Darguments is the workaround we have had to use. However, we set a
large number of profiles (and a few properties) for our release build, which
ends up meaning we have to list them all twice, once to the outer execution of
Maven, and once in -Darguments. Most of the profiles we enable are profiles
that include submodules into the reactor, so if we don't set them twice like
that, the inner Maven execution doesn't actually build the same modules.
I realize this isn't the same as passing the the settings file to the inner
execution, but it seems to me to be related.
> release:prepare does not pass argument "--settings" with current settings.xml
> to inner maven
> --------------------------------------------------------------------------------------------
>
> Key: MRELEASE-577
> URL: https://jira.codehaus.org/browse/MRELEASE-577
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-9, 2.0
> Reporter: Petr Kozelka
> Priority: Critical
> Labels: contributers-welcome
> Fix For: Backlog
>
>
> The impact is that release:prepare tries to use $HOME/.m2/settings.xml
> instead of the one supplied by --settings cmdline option, which leads to
> unexpected behavior
> Of course if it does not exist, the inhouse repository is avoided and release
> often fails due to a ResourceDoesNotExistException when an inhouse artifact
> is requested by the pom.
> To reproduce this problem, just rename your ~/.m2/settings.xml to ~/.m2/s.xml
> and run this:
> mvn --settings=$HOME/.m2/s.xml release:prepare .....
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
