bach VS meyvn

Projects like bach do serve to make the case that, if the resolution/build library piece were filled in, building and maintaining a multi module or multi-whatever project using just javac/jar/etc with Java build programs would be practical.

Have you heard about/looked into bach? It's a build-tool based mostly around pumping the output of one jdk tool into another.

Not quite that, but bach is a build tool trying to simplify that java build process.

The Meyvn REPL supports Java and Kotlin codebases. Source files are being monitored and compiled automatically, so you can create a class in Java, import it in a Kotlin object, which you can then manipulate at the REPL in Clojure. It achieves this by doing static analysis not on source files but on compiled classes. By keeping a dependency graph, it knows which classes need to be reloaded and in what order. This technology is very useful in the context of teams inheriting legacy codebases, typically Java or Kotlin. Meyvn: https://meyvn.org Installation: https://danielsz.github.io/meyvn

His other ask about developing against multiple codebases, that's what snapshot artifacts are for. And then the rest of the talk is about how he's made deps.edn, which is basically Apache Ivy in Clojure. I say Ivy and not Maven because it's only focused on dependency resolution, but then of course someone makes https://github.com/danielsz/meyvn to use the deps.edn for compile and publishing too, by delegating it back to Maven 🤦.