clojars 2026-05-09

Anyone else running into "Could not find artifact" errors today?

Came here to share the band aids we just added for our monorepo, using deps.edn: Had to add settings.xml mirrors so our CI runners were able to fetch clojure.jar



  
    
      google-central-mirror
      central
      Google Maven Central Mirror
      
    
  
And added this to all our deps.edn :
:mvn/repos {"central" {:url ""}
            "clojars" {:url ""}
            ;; Fallback to dodge intermittent 404s from repo1.maven.org.
            "google-central" {:url ""}}

Ty @tcrawley adding the mirror fixed things for me.

same here

Can y'all give examples of the failures? artifacts & versions?

And is this locally, or from CI?

"Failed to read artifact descriptor for org.clojure:clojure:jar:1.5.0", "Failed to read artifact descriptor for org.clojure:core.incubator:jar:0.1.2", "This could be due to a typo in :dependencies, file system permissions, or network issues.", "If you are behind a proxy, try setting the 'http_proxy' environment variable."], "stdout": "java.lang.Exception: Tried to use insecure HTTP repository.\n at cemerick.pomegranate.aether$fn__12486.invokeStatic (aether.clj:42)\n

When I deps :tree I don't have anything referencing core.incubator which is strange

Let me try and reproduce locally again

^ above is what I get after removing my .m2/repository

All those failures are artifacts on maven central, not clojars. Is this with lein? If so, what version? There was an upgrade to a new pomegranate recently, and I'm wondering if that broke something.

hmm, that change hasn't been released yet

Do you have :repositories set in your project.clj? If so, what do you have there?

No :repositories , it's possible the issue is with maven

java.lang.Exception: Tried to use insecure HTTP repository. makes me think something is setting the central url as http: instead of https:. Anything in ~/.lein/profiles.clj?

No. Only:

{:user
 {:global-vars {*warn-on-reflection* false
                *print-namespace-maps* false
                *assert* true
                *print-meta* false}}
 :profile
 {:dependencies [[com.clojure-goes-fast/clj-memory-meter "0.3.0"]]
  :jvm-opts ["-Djdk.attach.allowAttachSelf"]}}
but this also happens in a remote clean machine build script

If you run lein pom, do you see any http: repositories listed in pom.xml?

It's not clear to me , where org.clojure:core.incubator 0.1.2 is coming from

Ah, looking further in the output, I see as a repo for core.incubator. That makes me think a dependency has that repo defined in its pom.xml, and depends on core.incubator somehow.

What does lein deps :why org.clojure/core.incubator show?

returns nothing ...but, searching in my .m2 I find: clostache ... which isn't a dependency, but maybe of a plugin... I will check

hmmm, lein-binplus, but I have it as plugin in a profile that isn't being selected ; I will try removing it completely

That remove incubator related problem, but all the mavens are still failing. Which maybe just a maven issue?

maven central is working for me from here. Is there a proxy somewhere between you and the outside world?

is google's central less rate-limit heavy? we have issues building on github actions altogether because i assume they're blanket-blocking gha ips

It's just a GCS bucket last time I checked so I would expect so

👍 1