Welcome! Please see the About page for a little more info on how this works.

+1 vote
in tools.deps.alpha by

When {{clj}}/{{clojure}} encounters any kind of problem while building the classpath ({{deps.edn}} config, environment) it is almost impossible to diagnose the problem because only the exception message is printed.

For example, in a proxied environment {{clj}} fails to resolve Maven dependencies with a generic one-line message:

Error building classpath. Failed to read artifact descriptor for org.clojure:clojure:jar:1.9.0-beta2

(I believe this error is due to the web proxy.)

Consider adding a 'debug' or 'verbose' or 'stacktrace' option that provides visibility into the underlying machinery (stacktrace), so that users have a better handle on diagnosing problems.

4 Answers

0 votes
by

Comment made by: alexmiller

Not the point of this ticket, but one reason you may see this is the use of the Clojars CDN url, which requires SSL functionality not available in older JDKs. Using a recent version of Java 8 or 9 may work for you. A proxy could also be the cause though.

0 votes
by

Comment made by: gshayban

Seems like this has improved recently on master

0 votes
by

Comment made by: alexmiller

Not done yet. I have a bunch of tickets in flight that will be updated for the next release.

0 votes
by
Reference: https://clojure.atlassian.net/browse/TDEPS-21 (reported by glts)
...