[
https://jira.codehaus.org/browse/MRELEASE-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly closed MRELEASE-545.
-------------------------------------
Resolution: Duplicate
Closing this in favour of MRELEASE-577 as that has the suggestions for how to
patch
> When Using a Custom Settings XML File (with the -s option) release:prepare
> Does Not Read Proper Credentials
> -----------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-545
> URL: https://jira.codehaus.org/browse/MRELEASE-545
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.0
> Reporter: Tim O'Brien
>
> Here's the "situation":
> 1. You have multiple Maven Settings files because you are dealing with
> different environments. Assume you have:
> ~/.m2/envA-settings.xml
> ~/.m2/envB-settings.xml
> 2. Your build deploys to a repository manager with a server id of "nexus".
>
> 3. ~/m2/envA-settings.xml contains the server credentials for the server with
> an id of "nexus"
> Problem:
> Running the following command:
> mvn -s ~/.m2/envA-settings.xml release:perform
> After a successful prepare, gets a 401 error because the release:perform goal
> is not picking up the credentials from ~/.m2/envA-settings.xml.
> The work-around to this problem is to move ~/.m2/envA-settings.xml to
> ~/.m2/settings.xml. For some reason the perform goal only works for me
> when I am using the default location for Maven Settings XML. It seems
> like the release:perform should honor the custom location of a Maven Settings
> file.
> This quirk ate my day.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
