[
http://jira.codehaus.org/browse/MRELEASE-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267333#action_267333
]
H.-C. Gürsoy commented on MRELEASE-545:
---------------------------------------
Hi Folks,
I run today into same issue with version 2.1 of the plugin:
{noformat}
[INFO] [DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy' -->
[INFO] [DEBUG] (f) artifact = com.foocom:sample:jar:1.5
[INFO] [DEBUG] (f) attachedArtifacts =
[com.foocom:sample:java-source:sources:1.5,
com.foocom:sample:javadoc:javadoc:1.5]
[INFO] [DEBUG] (f) deploymentRepository =
Repository[releases|http://ci-repo-prod01.foocom.local:8081/nexus/content/repositories/simpleapp_release/]
[INFO] [DEBUG] (s) localRepository =
Repository[local|file:///home/guersoy/.m2/repository]
[INFO] [DEBUG] (f) packaging = jar
[INFO] [DEBUG] (f) pomFile =
/data/guersoy/workspaces/nexus-sample/target/checkout/pom.xml
[INFO] [DEBUG] (f) skip = false
[INFO] [DEBUG] (f) updateReleaseInfo = true
[INFO] [DEBUG] -- end configuration --
[INFO] [INFO] [deploy:deploy {execution: default-deploy}]
[INFO] [DEBUG] Using Wagon implementation lightweight from default mapping for
protocol http
[INFO] [DEBUG] Checking for pre-existing User-Agent configuration.
[INFO] [DEBUG] Adding User-Agent configuration.
[INFO] [DEBUG] not adding permissions to wagon connection
[INFO] Uploading:
http://ci-repo-prod01.foocom.local:8081/nexus/content/repositories/simpleapp_release//de/foocom/sample/1.5/sample-1.5.jar
[INFO] 2/2K
[INFO] [DEBUG] Using Wagon implementation lightweight from default mapping for
protocol http
[INFO] [INFO]
------------------------------------------------------------------------
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO]
------------------------------------------------------------------------
[INFO] [INFO] Error deploying artifact: Failed to transfer file:
http://ci-repo-prod01.foocom.local:8081/nexus/content/repositories/simpleapp_release/de/foocom/sample/1.5/sample-1.5.jar.
Return code is: 401
{noformat}
This is awfull because this issue is a show stopper for using the plugin in
central build systems hosting different projects with different credentials.
> When Using a Custom Settings XML File (with the -s option) release:prepare
> Does Not Read Proper Credentials
> -----------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-545
> URL: http://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.
-
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
