It seems like all the infrastructure around Maven Central is contrived to make caching dependencies hard...
-
Show this thread
-
Firstly, downloads default to HTTPS. Not a bad default, but I can't cache those downloads with a web proxy. That's fixable with an SBT flag.
3 replies 0 retweets 0 likesShow this thread -
Replying to @propensive
HTTPS is the only reasonable thing to do. Absent PGP signature checking, using HTTP would be reckless.
1 reply 0 retweets 1 like -
Replying to @larsr_h
I agree, though HTTP over a trusted LAN would be fine, if it proxies to an HTTPS request externally.
2 replies 0 retweets 0 likes -
Replying to @propensive
Not entirely convinced – how do you communicate TLS errors to clients?
1 reply 0 retweets 0 likes -
Replying to @larsr_h
Should they be any different from any other error? Why not just a 404?
1 reply 0 retweets 0 likes -
But does the client (i.e. SBT) actally disambiguate? "You can't have the artifact" sounds like the outcome in all cases...
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.