Nexus 400 Error
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about jenkins return code is 400 reasonphrase bad request Stack Overflow the company Business Learn more about hiring developers or posting ads with error deploying artifact failed to transfer file return code is 401 us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a
Failed To Deploy Artifacts: Could Not Transfer Artifact
community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Nexus accepts upload but says it failed up vote 16 down vote favorite 3 When
Maven Deploy Upload Twice
I execute mvn release:perform on a parent POM, the server is responding with this error about one of the child projects (filenames redacted): [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file (default-cli) on project: Failed to deploy artifacts: Could not transfer artifact from/to repository: Failed to transfer file. Return code is: 400, ReasonPhrase: Bad Request. However, all the files for this child project are successfully uploaded! I see a new directory (named error deploying artifact failed to transfer file return code is 500 after the release version number) and it contains all the .jar, .pom, .md5, and .sha1 files one would expect. I don't have access to the Nexus server, but I'm wondering what might cause this and how to fix it. Is it possible that Maven is trying to upload this particular child project twice? If so, why would Maven be doing this and how can I stop it? UPDATE: If you're having the same problem, check out the answer with the most upvotes in this post. I ran mvn help:effective-pom and found that the project in question actually had two executions of the deploy phase. Removing one of those executions solved my problem. java maven nexus share|improve this question edited Sep 23 '14 at 22:05 asked Sep 23 '14 at 19:32 Alien Bishop 1,70131736 Is the version that you are trying to deploy already present ? –StackFlowed Sep 23 '14 at 19:34 @wrongAnswer: No. When the error first occurred, I thought maybe that was the problem, so I explicitly deleted the artifact's new directory (along with the directory of another child project that uploaded without errors) and tried again. This resulted in the same problem: Both the child projects uploaded, but the second gave the "Bad Reqeust"
the fantastic documentation, the application itself seemed to have a good community
Delete Artifact From Nexus
supporting it. So, I decided to download and give it failed to deploy artifacts could not transfer artifact return code is 401 reasonphrase unauthorized a try. It was easy to follow the installation manual and within 5 minutes I failed to deploy artifacts: could not find artifact had everything installed and was ready to rumble. Here's a couple notes: Don't run Nexus as root. It's a security issue. Make a user for http://stackoverflow.com/questions/26003271/nexus-accepts-upload-but-says-it-failed them instead, or run it as your user in a home folder somewhere. Read through the documentation, at least the first few chapters to get the concepts down. Change the default passwords if this isn't a local nexus and can be reached within a network Working with SBT was what http://www.ethanjoachimeldridge.info/tech-blog/401-unauthorized-400-bad-request-sonatype-nexus I was interested in, and luckily Nexus has a chapter specifically on just that. Which got me mostly up and running. My build file ended up looking like this: organization := "test" name := "thing" version := "0.0.1" scalaVersion := "2.10.3" scalacOptions += "-deprecation" libraryDependencies <+= (scalaVersion)("org.scala-lang" % "scala-compiler" % _) resolvers += "Nexus" at "http://localhost:8081/nexus/content/groups/public" credentials += Credentials(Path.userHome / ".ivy2" / ".credentials") publishTo <<= version { v: String => val nexus = "http://localhost:8081/nexus/" if (v.trim.endsWith("SNAPSHOT")) Some("snapshots" at nexus + "content/repositories/snapshots") else Some("releases" at nexus + "content/repositories/releases") } With a .ivy2/.credentials file: realm=Sonatype Nexus Repository Manager host=127.0.0.1 user=admin password=admin123 I spent a lot longer than my initial 5 minutes on trying to get the publish task in sbt to run though. I kept getting: > publish [info] Wrote /Users/eeldridg/Sites/thing/target/scala-2.10/thing_2.10-0.0.1.pom [info] :: delivering :: test#thing_2.10;0.0.1 :: 0.0.1 :: release :: Thu Jul 02 11:56:02 EDT 2015 [info] delivering ivy fil
getting a 400 error https://issues.sonatype.org/browse/OSSRH-1253 when executing release:performAgile Board ExportXMLWordPrintable Details https://issues.sonatype.org/browse/NEXUS-10113 Type: Task Status: Closed Priority: Blocker Resolution: Fixed Labels: None Description When trying to release my project Nexus is returning a 400 HTTP error failed to code. [INFO] [INFO] [INFO] [INFO] -- maven-deploy-plugin:2.5:deploy (default-deploy) @ floggy -- [INFO] Uploading: http://oss.sonatype.org/content/groups/sourceforge-with-staging/net/sourceforge/floggy/floggy/1.4.0/floggy-1.4.0.pom [INFO] 4 KB [INFO] 8 KB [INFO] 12 KB [INFO] [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] Reactor Summary: return code is [INFO] [INFO] [INFO] [INFO] Floggy Framework's for JME ........................ FAILURE [4.657s] [INFO] [INFO] Build tools ....................................... SKIPPED [INFO] [INFO] Floggy Persistence Framework ...................... SKIPPED [INFO] [INFO] Floggy Persistence Framework Implementation ....... SKIPPED [INFO] [INFO] Floggy Persistence Weaver ......................... SKIPPED [INFO] [INFO] Floggy plugin for Maven ........................... SKIPPED [INFO] [INFO] Floggy Persistence Test ........................... SKIPPED [INFO] [INFO] Hospital-ME ....................................... SKIPPED [INFO] [INFO] Barbecue Calculator ............................... SKIPPED [INFO] [INFO] Floggy plugin for Eclipse ......................... SKIPPED [INFO] [INFO] Floggy feature for Eclipse ........................ SKIPPED [INFO] [INFO] Floggy's Skin Web Site ............................ SKIPPED [INFO] [
siteAgile Board ExportXMLWordPrintable Details Type: Bug Status: Closed Priority: Major Resolution: Unresolved Affects Version/s: 3.0.0 Fix Version/s: None Component/s: Raw, Repository Labels: None Description I can successfully Maven deploy a site to a Nexus Raw repository. However when I browse to it I get Error 404 Not Found Nexus Repository Manager OSS 3.0.0-03 OptionsSort By NameSort By DateAscendingDescendingDownload AllAttachments NexusSite.png 89 kB 04/20/16 02:51 PM NexusSite404.png 17 kB 04/20/16 02:51 PM Activity All Comments Work Log History Activity Ascending order - Click to sort in descending order Hide Permalink Rich Seddon added a comment - 04/21/16 05:03 PM Nexus 3 does not have directory browsing via HTML. Can you try going directly to the index.html path you deployed? Show Rich Seddon added a comment - 04/21/16 05:03 PM Nexus 3 does not have directory browsing via HTML. Can you try going directly to the index.html path you deployed? Hide Permalink Sonatype Support added a comment - 04/29/16 12:00 PM This issue has not been updated for 5 business days. If you have an update, please use the "Add Comment" action to let us know. If you have no other questions, please close this issue. If no update is received in the next 5 business days, this issue will be automatically closed. Thank you, The Sonatype Support Team Show Sonatype Support added a comment - 04/29/16 12:00 PM This issue has not been updated for 5 business days. If you have an update, please use the "Add Comment" action to let us know. If you have no other questions, please close this issue. If no update is received in the next 5 business days, this issue will be automatically closed. Thank you, The Sonatype Support Team Hide Permalink Sonatype Support added a comment - 05/07/16 12:00 PM This issue has not been updated for 10 business days. Automatically closing. Show Sonatype Support added a comment - 05/07/16 12:00 PM This issue has not been updated for 10 business days. Automatically closing. People Assignee: Rich Seddon Reporter: Desmond Kirrane Last Updated By: Sonatype Support Votes: 0 Vote for this issue Watchers: 2 Start watching this issue Dates Created: 04/20/16 02:51 PM Updated: 05/07/16 12:00 PM Date of First Response: 21/Apr/16 5:03 PM Agile View on Board Sonatype Privacy Policy Atlassian JIRA Project Management Software (v6.4.4#64019-sha1:7df