This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-09-17
Channels
- # announcements (17)
- # aws (2)
- # babashka (21)
- # beginners (67)
- # calva (19)
- # cider (29)
- # clara (3)
- # clj-kondo (6)
- # cljsrn (10)
- # clojure (140)
- # clojure-europe (164)
- # clojure-nl (3)
- # clojure-uk (8)
- # clojurescript (62)
- # conjure (7)
- # core-async (24)
- # cursive (21)
- # datomic (5)
- # docker (40)
- # emacs (14)
- # fulcro (25)
- # gratitude (1)
- # honeysql (6)
- # introduce-yourself (1)
- # jobs (1)
- # jobs-discuss (32)
- # juxt (7)
- # lsp (13)
- # minecraft (2)
- # off-topic (49)
- # pathom (24)
- # practicalli (8)
- # re-frame (18)
- # react (23)
- # remote-jobs (6)
- # reveal (2)
- # shadow-cljs (75)
- # tools-deps (7)
I’m getting a similar error as the one @souenzzo mentioned above, but looks like a different cause:
Error building classpath. Failed to read artifact descriptor for org.clojure:data.json:jar:2.4.0
org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.clojure:data.json:jar:2.4.0
In CI only (fetching all deps works locally).. wondering if anyone has any clues about why our CI build wouldn’t be able to access the clojure data.json jar? Anyone else having issues today fetching clojure data.json?I tried that 😕 .. seems to be the only thing the internet recommends as well. Or at least I believe I’ve tried that, if I’m understanding how invalidating the circle CI cache works. I have had issues with it in the past though!
can you just clj -Sdeps '{:deps {org.clojure/data.json {:mvn/version "2.4.0"}}}'
on the CI machine?
Interesting.. that gives > Failed to read artifact descriptor for org.clojure:clojure:jar:1.10.3 maybe there are bigger problems..
but also we’re using circle ci so it’s a new machine every time