Maven Error Code 400 Bad Request
Contents |
here for a quick overview of the site Help Center jenkins return code is 400 reasonphrase bad request Detailed answers to any questions you might have Meta Discuss maven deploy upload twice the workings and policies of this site About Us Learn more about Stack Overflow error deploying artifact failed to transfer file return code is 401 the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x
Failed To Deploy Artifacts: Could Not Transfer Artifact
Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up maven deploy + nexus failed on bad request up vote 4 down vote favorite 1 I am experiencing some failed to deploy artifacts could not transfer artifact return code is 401 reasonphrase unauthorized problems with my build process. the build is finishing fine and Jenkins starts to upload files to nexus. everything works well, but then it fails for some reason, the weirdest part is that the file that is mentioned to not be uploaded is actually uploaded and i can find it in nexus. here is the output: [INFO] ------------------------------------------------------------------------ [INFO] Reactor Build Order: [INFO] [INFO] pn-parent [INFO] pn-domain [INFO] pn-infra [INFO] pn-config [INFO] datalink-repository [INFO] pn-service [INFO] pn-backend [INFO] [INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder with a thread count of 1 [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building pn-parent 0.0.707 [INFO] ------------------------------------------------------------------------ [WARNING] The artifact junit:junit-dep:pom:4.11 has been relocated to junit:junit:pom:4.11 [INFO] [INFO] --- maven-jar-plugin:2.5:jar (default-cli) @ pn-parent --- [WARNING] JAR will be empty - no content was marked for inclusion! [INFO] Building jar: /var/lib/jenkins/jobs/webapps-server-side-release/workspace/pn-parent/target/pn-parent-0.0.707.jar [INFO] [INFO] --- maven-deploy-plugin:2.7:deploy (default-cli) @ pn-parent --- Uploading: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/pn-parent/0.0.707/pn-parent-0.0.707.pom Uploaded: http://
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 error deploying artifact failed to transfer file return code is 500 Learn more about Stack Overflow the company Business Learn more about hiring developers or
Failed To Deploy Artifacts: Could Not Find Artifact
posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow
Delete Artifact From Nexus
Community Stack Overflow is a 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 http://stackoverflow.com/questions/24806948/maven-deploy-nexus-failed-on-bad-request vote 16 down vote favorite 3 When 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 http://stackoverflow.com/questions/26003271/nexus-accepts-upload-but-says-it-failed are successfully uploaded! I see a new directory (named 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,69131736 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 tr
is the list few maven error and its troubleshooting. Tag Already exist If you see http://www.scmtechblog.net/2015/10/maven-errors-few-common-maven-error-and.html following type of error in your release build after the perform step [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on project : Unable to tag SCM [ERROR] Provider https://www.javacodegeeks.com/2015/03/setup-local-nexus-repository-and-deploying-war-file-from-maven.html message: [ERROR] The git-tag command failed. [ERROR] Command output: [ERROR] fatal: tag '
ProjectsDealsJob BoardJobsJoin UsJCGW4GSubmission GuidelinesTerms & ConditionsAboutAbout JCGsAdvertisingTerms of UsePrivacy Policy Java Code Geeks Java Developers Resource Center AndroidAndroid CoreAndroid GamesJavaCore JavaDesktop JavaEnterprise JavaJVM LanguagesCeylonClojureGroovyJRubyKotlinScalaSoftware DevelopmentAgileCareerCommunicationsDevOpsMeta JCGBest Of The WeekMisc Home » Java » Enterprise Java » Setup Local Nexus Repository and Deploying WAR File from Maven About Arun Gupta Arun is a technology enthusiast, avid runner, author of a best-selling book, globe trotter, a community guy, Java Champion, JavaOne Rockstar, JUG Leader, Minecraft Modder, Devoxx4Kids-er, and a Red Hatter. Setup Local Nexus Repository and Deploying WAR File from Maven Posted by: Arun Gupta in Enterprise Java March 2nd, 2015 Maven Central serves as the central repository manager where binary artifacts are uploaded by different teams/companies/individuals and shared with rest of the world. Much like github, and other source code repositories, which are very effective for source code control, these repository managers also act as a deployment destination for your own generated binary artifacts.Setting up a local repository manager has several advantages. The primary ones are that they act as a highly configurable proxy between Maven central so that everybody does not have to download all the dependencies from the central repo. Another primary reason is to control your interim generated artifacts within your team. Reasons to Use a Repository Manager provide detailed explanation of a complete set of benefits.This Tech Tip will show how to setup a local Nexus repository manager, and push artifacts to it – both snapshots and releases.Lets get started!Install and Configure Local Nexus RepositoryDownload and unzip latest Nexus OSS. Default administrator’s login/password is admin/admin123. Default deployment login/password is deployment/depl