Clojurians Log v2

https://github.com/cognitect/transit-java 1.1.403 and https://github.com/cognitect/transit-clj 1.1.357 no functional changes just dropping the -alpha tag used in the last release.

Announcing https://github.com/enragedginger/pants_backend_clojure - Monorepo-grade builds for Clojure via the https://www.pantsbuild.org/ build system If your Clojure codebase has grown to a certain point where you have multiple services, shared libraries, conflicting dependency versions, etc, you've probably felt the pain. I hit this at 35k lines after moving from lein to poly. poly never quite clicked for me: the base/component distinction felt arbitrary, errors were unhelpful, and it messed with my test classpath in ways I couldn't explain. I added Clojure support into Pants to get: - Automatic dependency inference. No more maintaining dependency lists by hand. Pants reads require and import forms and figures out both first-party and third-party deps for you. - Fine-grained caching. Pants tracks dependencies at the file level. A change in one namespace only invalidates the tests that actually depend on it. pants test :: on a large repo is fast after the first run. - Multiple resolves. Need some code to work against both Java 11 and Java 21, or against different library versions? Define multiple resolves and Pants will test against each. No classpath hacks, no "it works in dev but breaks in prod." - pants generate-deps-edn — generates a deps.edn from your Pants project, so clj-kondo, cljfmt, Cursive, Calva, CIDER, and anything else that reads deps.edn keeps working exactly as before. Built-in goals: repl (nREPL + rebel-readline), test, lint (clj-kondo), fmt (cljfmt), check, and package (uberjars with AOT). I'm dogfooding this on my own large project and it's been working well for the past several months. The project has been in a steady state for awhile now that I'm comfortable publishing it for others to use too. I would love to get feedback from other Clojure devs, especially if you have a large codebase that's tricky to manage for any of the reasons I mentioned above. You can read the full rationale https://github.com/enragedginger/pants_backend_clojure?tab=readme-ov-file#a-handcrafted-word-from-the-author.