>
> I should have mentioned that I had tried both these before posting, and
> they don't seem to help in this case. All clojure version artifacts were
> still being downloaded.
>
Huh. That's surprising. Don't know why.
*-SNAPSHOT dependency resolution is a bit strange, which is why it's
On Fri, 11 Mar 2011 16:40:46 -0500, Stuart Sierra
wrote:
I created the testbuild-* artifacts, but they were never uploaded to the
Maven Central Repository. I had previously deleted the staging
repositories
from oss.sonatype.org, and today I deleted the remaining
1.3.0-testbuild*-SNAPSHOT
I created the testbuild-* artifacts, but they were never uploaded to the
Maven Central Repository. I had previously deleted the staging repositories
from oss.sonatype.org, and today I deleted the remaining
1.3.0-testbuild*-SNAPSHOT artifacts from oss.sonatype.org.
FYI, you can also exclude tra
> Hi,
>
> I have a project that depends on enlive, which uses a dependency range in its
> clojure dependency. This seems to cause all possible versions of clojure to
> be pulled down, including clojure-1.3.0-testbuild1-SNAPSHOT, which is broken
> (parent pom is in a release repo which isn't li
Hi,
I have a project that depends on enlive, which uses a dependency range in
its clojure dependency. This seems to cause all possible versions of
clojure to be pulled down, including clojure-1.3.0-testbuild1-SNAPSHOT,
which is broken (parent pom is in a release repo which isn't listed in
