@akhudek: you may be able to remove http://clojars.org from the list of repositories via your project.clj
see https://github.com/technomancy/leiningen/tree/master/sample.project.clj#L76
with ^:replace
metadata, you should be able to override the default set
@sonnyto: thanks for offering! I'm about to start a thread about ways to prevent an outage as bad as today on the clojars-maintainers list: https://groups.google.com/group/clojars-maintainers
if you want to join
btw lein-localrepo plugin helps with http://clojars.org reachability issues, since (i think) it makes lein treat local maven cache as a repository.
i happen to have had lein-localrepo plugin cached in ~/.m2 for a while, it just came in handy
thanks peterbak
the maven-metadata.xml wouldn't be there, so unless lein-localrepo does something about that, anything that needs the metadata would fail
but that should only be a problem for lein-ancient and the like
and depending on "LATEST" or "RELEASE" versions
which you should never do
@peterbak - can you tweet about that?
composing...
clojars is up at the moment. get your deps while they are hot
NICE
now would be the time to install lein-localrepo :simple_smile:
heh
@tcrawley thanks for keeping clojars running
Looks like Linode's latest ploy is working (DDoS mitigation hardening on a dedicated transit link.)
Well, it worked for a bit. Crossing fingers. :simple_smile: