it happened again...
On Friday, 15 June 2012 05:32:14 UTC+1, Nelson Morris wrote:
On Thu, Jun 14, 2012 at 8:38 AM, Stuart Sierra
the.stua...@gmail.com javascript: wrote:
Is there anyone on the Clojure/core team with a contact among those
who run Central who could get them to
I'm surprised this still hasn't been fixed. I noticed it and raised the issue
(well, told people about it on IRC) about 2 weeks ago. I've been pointed at an
alternate repo as a workaround. :/
---
Joseph Smith
j...@uwcreations.com
On Aug 16, 2012, at 5:27 AM, Paul Lam paul@forward.co.uk
On Thu, Aug 16, 2012 at 1:46 PM, Joseph Smith j...@uwcreations.com wrote:
I'm surprised this still hasn't been fixed. I noticed it and raised the
issue (well, told people about it on IRC) about 2 weeks ago. I've been
pointed at an alternate repo as a workaround. :/
Hmm, it is fine here:
Just want to make this is clear: no one on the Clojure mailing list (or
IRC) has any direct control over the major public repositories.
The Maven Central Repository (repo1.maven.org) is managed by the Apache
Foundation with help from Sonatype, Inc. See
On Thu, Aug 16, 2012 at 8:12 AM, Stuart Sierra
the.stuart.sie...@gmail.com wrote:
Just want to make this is clear: no one on the Clojure mailing list (or IRC)
has any direct control over the major public repositories.
You can report issues with Central here:
Thanks, Phil,
-S
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group,
Is there anyone on the Clojure/core team with a contact among those
who run Central who could get them to look into this?
I'm on the Sonatype OSSRH mailing list:
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide
(mailing list addresses at the bottom)
On Thu, Jun 14, 2012 at 8:38 AM, Stuart Sierra
the.stuart.sie...@gmail.com wrote:
Is there anyone on the Clojure/core team with a contact among those
who run Central who could get them to look into this?
I'm on the Sonatype OSSRH mailing list:
On Jun 12, 2012, at 7:12 PM, Phil Hagelberg wrote:
On Mon, Jun 11, 2012 at 1:48 PM, Phil Hagelberg p...@hagelb.org wrote:
On Mon, Jun 11, 2012 at 9:36 AM, Phil Hagelberg p...@hagelb.org wrote:
These will be removed once Central gets back to working order, but
they should help stem the flow of
On Wed, Jun 13, 2012 at 5:47 AM, Chas Emerick c...@cemerick.com wrote:
On Jun 12, 2012, at 7:12 PM, Phil Hagelberg wrote:
On Mon, Jun 11, 2012 at 1:48 PM, Phil Hagelberg p...@hagelb.org wrote:
On Mon, Jun 11, 2012 at 9:36 AM, Phil Hagelberg p...@hagelb.org wrote:
These will be removed once
On Mon, Jun 11, 2012 at 1:48 PM, Phil Hagelberg p...@hagelb.org wrote:
On Mon, Jun 11, 2012 at 9:36 AM, Phil Hagelberg p...@hagelb.org wrote:
These will be removed once Central gets back to working order, but
they should help stem the flow of catastrophic build failures.
While this will allow
Some time over the weekend Maven Central lost knowledge of all
versions of Clojure other than 1.2.0:
$ curl
http://repo.maven.apache.org/maven2/org/clojure/clojure/maven-metadata.xml
?xml version=1.0 encoding=UTF-8?
metadata
groupIdorg.clojure/groupId
artifactIdclojure/artifactId
On Mon, Jun 11, 2012 at 9:28 AM, Phil Hagelberg p...@hagelb.org wrote:
Some time over the weekend Maven Central lost knowledge of all
versions of Clojure other than 1.2.0:
I've deployed the other versions to Clojars as a temporary measure:
https://clojars.org/org.clojure/clojure
These
Seems like a manifest issue, because all versions are there:
http://repo1.maven.org/maven2/org/clojure/clojure/
Marek.
On Monday, June 11, 2012 6:28:42 PM UTC+2, Phil Hagelberg wrote:
Some time over the weekend Maven Central lost knowledge of all
versions of Clojure other than 1.2.0:
$
On Mon, Jun 11, 2012 at 9:36 AM, Phil Hagelberg p...@hagelb.org wrote:
These will be removed once Central gets back to working order, but
they should help stem the flow of catastrophic build failures.
While this will allow most builds to work, it's a band-aid solution.
Is there anyone on the
15 matches
Mail list logo