I've read the README and the mailing list thread, but the primary motivation for multiple classloaders isn't clear to me. It might help to explain it, given some of the challenges and because you're still left with a "single composite Clojure application".
Is it to support switching to a different version of a Java dependency without restarting jig?
Is it to be able to support different versions of Java dependencies in multiple projects?
Is it due to the hope that multiple Clojure instances will eventually run cleanly in the same JVM?
(I haven't run into problems with it, I'm just curious.)
I've read the README and the mailing list thread, but the primary motivation for multiple classloaders isn't clear to me. It might help to explain it, given some of the challenges and because you're still left with a "single composite Clojure application".
Is it to support switching to a different version of a Java dependency without restarting jig?
Is it to be able to support different versions of Java dependencies in multiple projects?
Is it due to the hope that multiple Clojure instances will eventually run cleanly in the same JVM?
(I haven't run into problems with it, I'm just curious.)