Maven Deploy 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 Stack Overflow maven deploy return code is 400 reasonphrase bad request the company Business Learn more about hiring developers or posting ads with us Stack failed to deploy artifacts: could not transfer artifact Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community error deploying artifact failed to transfer file return code is 401 of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Error when deploying an artifact in Nexus up vote 41 down vote favorite 8 Im' getting an
Maven Deploy Upload Twice
error when deploying an artifact in my own repository in a Nexus server: "Failed to deploy artifacts: Could not transfer artifact" "Failed to transfer file http:///my_artifact. Return code is: 400" I have Nexus running with one custom repository my_repo with the next maven local configuration: settings.xml
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies failed to deploy artifacts: could not find artifact of this site About Us Learn more about Stack Overflow the company
Failed To Deploy Artifacts Could Not Transfer Artifact Return Code Is 401 Reasonphrase Unauthorized
Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users
Failed To Deploy Artifacts Could Not Transfer Artifact Reasonphrase Forbidden
Badges Ask Question x 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 http://stackoverflow.com/questions/18649486/error-when-deploying-an-artifact-in-nexus minute: Sign up Why do I get a 400 when attempting to use publish-plugin from the Grails Release plugin up vote 2 down vote favorite 1 I'm using Grails 2.4.1 & The Grails Release plugin version 3.0.1. I have a Sonatype nexus repository (v2.3.1-01) setup that's in use by several other projects with no issues. I'm attempting to create a new Plugin http://stackoverflow.com/questions/25332917/why-do-i-get-a-400-when-attempting-to-use-publish-plugin-from-the-grails-release that I want to distribute through a SNAPSHOT repository in nexus (and later through our Releases repository). In my ${projectName}GrailsPlugin.groovy file I have: def groupId ="my-department-grails-plugins" def version = "0.1-SNAPSHOT" In my application.properties file I have: app.name=MyPluginNameForGrails In my BuildConfig.groovy I have: grails.project.repos.newsnapshots.url = "http://internal.server.address/nexus/service/local/repositories/snapshots" grails.project.repos.newsnapshots.username = "username" grails.project.repos.newsnapshots.password = "password" I'm trying to kick things off with the following command: publish-plugin --snapshot --repository=newsnapshots --stacktrace The build success everything looks good until it trys to push into nexus and I get: Using configured username and password from grails.project.repos.newsnapshots ....Error | Failed to publish plugin: Error deploying artifact 'ald-grails-plugins:my-plugin-name-for-grails:zip': Error deploying artifact: Failed to transfer file: http://internal.server.address/nexus/content/groups/public/my-department-grails-plugins/my-plugin-name-for-grails/0.1-SNAPSHOT/my-plugin-name-for-grails-0.1-20140815.191240-1.zip. Return code is: 400 I've found a related StackOverflow question which seems related but none of the conditions they describe as causing the 400 exist. I also found the article by Sonatype Nexus which describes possible causes of 400's and those don't seem to be it either. If you notice the repository that I'm pointing to, it is directly to a repository but then in the error message it lists a path to a group. I am
Failed to deploy artifacts: Could not transfer http://betterlogic.com/roger/2012/04/maven-upload-file-400/ artifact org.apache:activemq-distro:tgz:5.5.1 from/to unapproved-snapshots (https://mvn.fsglobal.net/content/repositories/unapproved-snapshots/): Failed to transfer file: https://mvn.fsglobal.net/content/repositories/unapproved-snapshots/org/apache/activemq-distro/5.5.1/activemq-distro-5.5.1.tgz. Return code is: 400 -> [Help 1] meant "usually happens when you are trying to deploy to the wrong repo. " Post navigation Previous Postmaven/nexus failed to upload tgz/tar.gz fileNext Postjruby woe 2 thoughts on “maven upload file 400” rogerdpack says: November 29, 2012 at 10:28 am If you get an error code 400 using deploy-file, you may be trying to deploy a return code is SNAPSHOT artifact to a non-SNAPSHOT repository rogerdpack says: November 29, 2012 at 10:29 am can also mean that you're trying to upload a file "over the top" of one that's already there (and is non snapshot) You can choose a new version or delete the old one in that case. So basically 400 error means "some failure occurred!") Leave a Reply Cancel reply Your email address will not be published. Required fields are marked *Comment Name * Email * Website seven + 8 = Roger's meanderings, notes to himself, bug reports, and other things Blogroll Free Bible mine and my wife's site Proudly powered by WordPress