Sonatype reports the cache has been purged and it should be working again.
Seems to be for me.
On Mon, Aug 11, 2014 at 8:35 AM, Ivan Mikushin wrote:
> The same issue (and workaround) applies to clojurescript-0.0.2311
>
> --
> Note that posts from new members are moderated - please be patient wi
The issue is resolved for me also. Thanks!
--Curtis
On Sat, Aug 9, 2014 at 10:18 AM, Paul Burt wrote:
> On Saturday, 9 August 2014 16:03:57 UTC+1, Rick B wrote:
> > There was a cache issue for the maven-metadata.xml and the possibly the
> jar files for 0.0-2301 and 0.0-2307. We have purged o
I will file an issue - thanks for the analysis!
Alex
On Saturday, August 9, 2014 8:41:34 AM UTC-5, Curtis Summers wrote:
> I think this may be a cache issue with the central repo. I can both see the
> file via browsing and they are in the index for me, but the actual jar file
> brings up a 404
I think this may be a cache issue with the central repo. I can both see the
file via browsing and they are in the index for me, but the actual jar file
brings up a 404:
http://repo1.maven.org/maven2/org/clojure/clojurescript/0.0-2307/clojurescript-0.0-2307.jar
However, appending a junk query s
Maybe is a geographical problem.
Currently if i run
lein try org.clojure/clojurescript 0.0-2307
it fails in Italy (where I live), but it succeeds on a DigitalOcean
instance in their US (SF1) datacenter.
Francesco
On Saturday, August 9, 2014 1:01:06 PM UTC+2, Nicola Mometto wrote:
>
>
> I can
I can confirm, there seem to be problem fetching clojurescript versions
0.0-2301 and 0.0-2307.
Browsing the Central repo the files are there:
http://repo1.maven.org/maven2/org/clojure/clojurescript/0.0-2301/
http://repo1.maven.org/maven2/org/clojure/clojurescript/0.0-2307/
But the maven-metadata
