Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use the http status message to relay more context on deploy failure #367

Closed
tobias opened this issue Aug 3, 2015 · 2 comments
Closed

Use the http status message to relay more context on deploy failure #367

tobias opened this issue Aug 3, 2015 · 2 comments

Comments

@tobias
Copy link
Member

tobias commented Aug 3, 2015

Currently, reploying a non-SNAPSHOT, or deploying with an invalid group, project, or version results in:

Failed to deploy artifacts: Could not transfer artifact blahblah:blahblah:pom:0.1.0 from/to local (https://clojars.org/repo/): Access denied to: http://localhost:8080/repo/blahblah/blahblah/0.1.0/blahblah-0.1.0.pom, ReasonPhrase: Forbidden

It would be nice if we could make that "Forbidden" be "Forbidden - redeploying non-snapshots is not allowed" instead, with similar messages for validation failures.
tobias added a commit that referenced this issue Aug 3, 2015
@tobias
(ab)use the status message to relay more context to aether (#367)
b6fd245 
This sends more informative messages to the deploying client using the
status message, which aether parses and displays on deploy failure.
@danielcompton
Copy link
Member

It would be good to add a link to docs for further explanation too.

@tobias
Copy link
Member Author

tobias commented Aug 3, 2015

Good call, we could link to pages in the wiki.

On Monday, August 3, 2015, Daniel Compton [email protected] wrote:

It would be good to add a link to docs for further explanation too.

—
Reply to this email directly or view it on GitHub
#367 (comment).

@tobias tobias mentioned this issue Aug 4, 2015
Closed
tobias added a commit that referenced this issue Aug 4, 2015
@tobias
Include links to the FAQ in error messages (#367)
6c29414
@tobias tobias closed this as completed Aug 12, 2015
@tobias tobias mentioned this issue Sep 22, 2015
Closed
swr1bm86 pushed a commit to swr1bm86/clojars-web that referenced this issue Oct 3, 2015
@tobias
(ab)use the status message to relay more context to aether (clojars#367)
8fd7cee 
This sends more informative messages to the deploying client using the
status message, which aether parses and displays on deploy failure.
swr1bm86 pushed a commit to swr1bm86/clojars-web that referenced this issue Oct 3, 2015
@tobias
Include links to the FAQ in error messages (clojars#367)
f9bb3a9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tobias @danielcompton