Thank you all for the replies - now I understand where the problem comes
from.
Best regards,
Piotr
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are
We AOT often dependent projects.
We are very careful meeting the exclusions suggestions reported
by lein deps :tree.
Luc P.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts
It's possible to do a mixed AOT (your code) non-aot (third-party code)
setup, but it's a huge pain.
The particular issue you're seeing is probably the result of multiple
versions of a class existing across jars and classloaders. Unfortunately
there is no consistent way to get this right, but the
Hi Piotr,
Yes, the limitation is how the Java classpath works. If you AOT your app,
you need to AOT compile other Clojure code your app uses.
See e.g.
Hello,
I am trying to solve an issue in my project where I have the following
setup. My application modules are AOT-compiled into several jars and then
packaged with their 3rd party dependencies into an uberjar. As a result my
uberjar contains my project's namespaces compiled to class files
