-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better error message in case of HTTP request failure #5
Comments
Definite +1 :)
it turned out that I have forgotten to upload my public key but I had to access Nexus to check this out. also this
could be changed to sth like this
or sth like that - it might seem confusing for some people. |
Thanks for your comment. I hope that REST response from Nexus contains that information (not only plain status 400...). |
Btw, in the meaning in case of similar issues as a workaround you could use a |
In a case of 500 from the server (with HTML content) a message is also not very meaningful:
More details #15. |
fixed in pull request #32 I print the entire body, status code and status string and sonatype had some great error message in the body. |
nice! :) |
Hi, guys, I'm trying to move my deployment process from bintray back to sonatype
Sure that error message could be better but what is the roor cause, what I'm doing wrong? |
ok, got it. I've copied this config from the hermes project and it helped. Looks like you need to adjust the defaults
|
@bartoszwalacik Have you read FAQ? :) (Update: the problem described in FAQ is a little bit different - if you think it would be good to add your explicitly it can be done) |
Btw, in a case of further problems running with |
And yes, it will be adjusted: #12 (most likely in Q2 2017 just after 0.6.0 with rewritten backend will be finally released). |
Following suggestions from [#5](Codearte/gradle-nexus-staging-plugin#5) to fix nexus release issue
Implemented in #32. Available in 0.6.0. |
No description provided.
The text was updated successfully, but these errors were encountered: