For anyone interested. My workaround for the too long classpath: I unpacked (unzipped or copied) entries from the classpath to target/classes and then use that as the sole classpath for the next step.
It was pretty easy to work around, but I think the @classpath-file.txt approach is worth exploring.
+1 I'm using the @classpath-file.txt on another project -- not for long args but for other reasons
@ghadi congrats on the new born one!
thanks @borkdude!
I heard it was coming in the podcast with Sean
@borkdude I'll look at that today
there's an issue in tools.deps for that but not for tools.build
@alexmiller if you want a repro, I can make you one
or in fact, I can just point you to the commit that failed
note that it is a Windows only problem (with regards to the length of the classpath)
yeah
https://github.com/clojure/tools.build v0.6.4 ea76dff is now available • java-command - add control over using classpath file with :use-cp-file (default=:auto) • compile-clj - can now accept java-command passthrough args :java-cmd, :java-opts, :use-cp-file
^^ will automatically use classpath file for long compile-clj command lines on Windows
https://github.com/clojure/tools.build v0.6.5 a0c3ff6 is now available • git-process - NEW task to run an arbitrary git process and return the output • git-rev-count - updated to use git-process, added :git-command attribute
there have been several requests for various git tasks, rather than add these as random 1-offs, you can now use the generic git-process task, some examples in the doc https://clojure.github.io/tools.build/clojure.tools.build.api.html#var-git-process