[
http://jira.codehaus.org/browse/MRELEASE-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=268199#action_268199
]
Christoph Kutzinski commented on MRELEASE-521:
----------------------------------------------
I've just confirmed that it still happens with release-plugin 2.1.
Another workaround is to append -Darguments="-s<my_settings_file>" to the
release:perform call. E.g.
mvn -s<my_settings_file> release:prepare release:perform
-Darguments="-s<my_settings_file>"
See also
http://maven.40175.n5.nabble.com/mvn-release-perform-does-not-honor-servers-server-in-alternate-settings-location-td70612.html
> release:perform does not take the settings specified by the -s option
> ----------------------------------------------------------------------
>
> Key: MRELEASE-521
> URL: http://jira.codehaus.org/browse/MRELEASE-521
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.0-beta-7
> Reporter: Kay Kay
>
> # mvn -s <some.custom.settings.xml> release:perform
> does not take the settings.
> If we copy the same to - ~/.m2/settings.xml
> # mvn release:perform
> works fine.
> Something does not add up.
--
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
