Return code is: 401, ReasonPhrase: Unauthorized.
/> org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to deploy artifacts: Could not transfer artifact it.pigiuz.test.AutoDeploy:TestLibOne:swc:1 from/to pippo (http://localhost:8081/nexus/content/repositories/pippo/): Failed to transfer file: http://localhost:8081/nexus/content/repositories/pippo/it/pigiuz/test/AutoDeploy/TestLibOne/1/TestLibOne-1.swc. Does the ISS have a rotational motion in addition to its translational motion? You can check this by running mvn help:effective-settings. Here is my POM.
Show Peter Lynch added a comment - 12/12/16 06:19 PM An upstream Maven HTTP Wagon issues has been reported and fixed to prevent this on the Maven side: https://issues.apache.org/jira/browse/WAGON-469 Not sure May be the solution is here http://stackoverflow.com/questions/1650596/how-do-i-import-a-new-java-ca-cert-without-using-the-keytool-command-line-utilit Hide Permalink Rich Seddon added a comment - 04/15/13 06:09 PM An SSL certificate error will not give you a 401 response. Nexus 3 [DEBUG] Configuring mojo org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy-file from plugin realm ClassRealm[plugin>org.apache.maven.plugins:maven-deploy-plugin:2.8.2, parent: [email protected]] [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy-file' with basic configurator --> [DEBUG] (f) artifactId = project [DEBUG] (f) file = /app/clm-testing/jenkins/hudson-2.2.1.war [DEBUG] If there is no error output, ensure your user privileges are correctly configured on the server.
Briefly speaking, a '401' error occurs when the server asks for user authentication but the client can not provide it. Go to search box, by skipping navigation top bar. I'm using a new installation of Nexus 3 (installed yesterday, 12/7/2016), this particular project having the issue has credentials to deploy to nexus, it in fact correctly deploys pom files and What in the world happened with my cauliflower?
My username is "phax" Thanks, Philip Attachment Information Project: Joinup Component: Miscellaneous Category: Support Priority: Critical Assigned: Unassigned Status: Active Identifier: 104172 Comments Login or register to post comments #1 I don't know what "drop" means. at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$6.wrap(WagonRepositoryConnector.java:1016) at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$6.wrap(WagonRepositoryConnector.java:1004) at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:895) at org.eclipse.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:522) at org.eclipse.aether.internal.impl.DefaultDeployer.deploy(DefaultDeployer.java:331) ... 26 more Caused by: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/github/aliteralmind/xbnjava/0.1.2/xbnjava-0.1.2.pom. Mng-4469 Return code is: 401, ReasonPhrase: Unauthorized.
Join them; it only takes a minute: Sign up Why am I getting a “401 Unauthorized” error in Maven? Error Deploying Artifact Failed To Transfer File Return Code Is 400 Log in to Nexus and give the deployment user the role(s) required to to change that snapshot repo. Please proceed to close this ticket. http://stackoverflow.com/questions/20570009/deploying-artifacts-in-nexus-from-maven-gives-error-return-code-is-401 All of sudden, our CI server here at PIH is unable to deploy to mavenrepo with error listed below--last successful upload was at 1:40pm yesterday.
You will get a 401 Unauthorized error if you supply the wrong credentials (password etc). Nexus Npm Publish 401 Solved my issue –Dhiral Pandya Jun 26 '15 at 10:55 Worked for me too! –Igor Baiborodine Mar 16 '16 at 20:24 add a comment| up vote 2 down vote I am just hitting wall after wall with Maven. I misspelled the password.
Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy-file (default-cli) on project standalone-pom: Failed to deploy artifacts: Could not transfer artifact com.somecompany:project:war:1.0.0 from/to local-nexu (http://localhost:8081/nexus/content/repositories/releases/): LifeCoach project Rent clothing in Frankfurt / Being warm without cold weather clothing Bash regex test not working A Little Cryptic Puzzle Movie about a girl who had another different life Error Deploying Artifact Failed To Transfer File Return Code Is 401 share|improve this answer edited Jul 18 '14 at 18:29 aliteralmind 11.1k63971 answered Jul 18 '14 at 17:54 Moe Singh 1356 I am aliteralmind. Return Code Is 401 Reasonphrase Unauthorized. Artifactory The project's settings: Checklist item 3.
Show Thomas Keys added a comment - 12/08/16 05:38 PM I'm seeing this issue occur with a scenario that I'm not sure has been mentioned here. Having tried all the suggestions above and more without success I eventually found that it was a Jenkins setting that was in error. Apparently I have specified -DrepositoryID (note ID in capital) instead of -DrepositoryId. have a peek at these guys Show Rich Seddon added a comment - 05/29/12 03:30 PM I don't see your settings.xml.
Show Matt Franklin added a comment - 12/08/16 01:56 PM To be clear, this issue occurs any time a user is not authorized to execute the deployment. Maven Deploy Username Password Return code is: 401, ReasonPhrase: Unauthorized. Make sure your settings.xml is in the correct place (normally it’s _~/.m2/settings.xml).
You should not need to do that. –Manfred Moser Dec 16 '13 at 16:58 Oh my good! , you save my night , thx it works perfectly –Adnen Chouibi I've been taking a lot from SO recently, so I'm glad that I've been able to help someone else, your question has been the first time someone's accepted my answer! –John Show Peter Lynch added a comment - 11/14/16 09:53 PM Through a reverse proxy scenario, the 401 response from Nexus can trigger a 502 Bad Gateway response from the reverse proxy, Error Deploying Artifact Failed To Transfer File Return Code Is 500 Show Oren Livne added a comment - 12/01/09 05:59 PM Thanks so much.
Couple of hints... Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are The SSL problem was another I had, but 401 is 401, sorry. check my blog Hide Permalink Thomas Keys added a comment - 12/08/16 06:38 PM Update to my comment above - managed to get this to work using newest version of Maven (3.3.9).
Hide Permalink Thomas Keys added a comment - 12/08/16 05:38 PM I'm seeing this issue occur with a scenario that I'm not sure has been mentioned here. Tried with both RELEASE and SNAPSHOT policy on the thirdparty repo, with the same result. For example, here is the mvn output of deploying a file: [[email protected] lib]$ mvn deploy:deploy-file -DgroupId=com.oracle -DartifactId=xmlparserv2 -Dversion=18.104.22.168.0 -Dfile=xmlparserv2.jar -DrepositoryId=thirdparty -Durl=http://dev-tools.further.utah.edu/nexus/content/repositories/thirdparty -Dpackaging=jar [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building I didn't think I made any changes, but obviously eliminating that -SNAPSHOT from the version was a bad thing. –aliteralmind Jul 18 '14 at 18:47 8 Why in the WORLD