[
https://issues.jenkins-ci.org/browse/JENKINS-12031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160919#comment-160919
]
Mark Maun commented on JENKINS-12031:
-------------------------------------
I've also seen this issue. We upgraded from 1.408 to 1.457 on a Beta server
and we are seeing the same issue. The compilation is successful but on
transferring the artifact to Nexus it's returning a 401 unauthorized message
and failing. The settings.xml has not changed and file transfers were
working great with 1.408.
I'm using Maven 3.0.4. I even got on a support call with Sonatype and was
able to transfer the artifacts directly, just not using Jenkins.
> Maven deploys fail after upgrade to 1.442
> -----------------------------------------
>
> Key: JENKINS-12031
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12031
> Project: Jenkins
> Issue Type: Bug
> Components: maven2
> Affects Versions: current
> Reporter: Justin Plock
> Labels: build, maven, plugin
>
> Ever since upgrading to 1.442, I'm unable to deploy packages up in to my
> Maven repository hosted in Nexus.
> org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to
> deploy artifacts: Could not transfer artifact
> com.company.core:dbt-core:jar:1.0.0-20111207.203519-81 from/to
> com.company.sandbox
> Nexus is returning a 401 response code and I've ensured my credentials are
> indeed valid.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
