https://clojurians.slack.com/archives/C02B5GHQWP4/p1669247667680269?thread_ts=1669247667.680269&cid=C02B5GHQWP4

0.8.4 was the first (and so far only) release of tools.build to Maven. It is not normally released to Maven and I think it might be a manual process?

Normally, you'd use tools.build as a git dep... what is your use case for using it as a non-git dep @U2J4FRT2T?

oh tools build has a channel. nice. @U04V70XH6 no specific use-case. just tried to use, and it fails. so reporting.

there was a snafu in the release process, I will fix it on 0.8.6, but really 0.8.5 is not much different than 0.8.4 so it has not seemed worth it to fix to me

@U04V70XH6 fwiw, personally, I tried switching to the maven dep to avoid the :git/sha part. No other reason.

@UE21H2HHD I guess I have so much dev tooling that uses git deps that it hasn't mattered to me...

i love git deps and usually use it for everything. local/root is awesome too! some things like being able to overwrite a dep just by placing its symbol and pointing to a "dumb root" is way better than handle maven logics but some companies only allow maven deps, because they have infrastructure on it (dep usage/analysis etc)

(we're using a core.async fork via git deps in production, plus Polylith, an external test runner, tools.build, build-clj, the Cognitect test-runner, clj-watson, the Datomic dev.datafy stuff, Stu's reflector project, the add-lib3 branch of tools.deps.alpha ... all via git deps 🙂 )