This organization was marked as archived by an administrator on Nov 6, 2025. It is no longer maintained.
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Apparently the
checkClojuretask loads the clojure namespaces and all imported classes with it when building.Ignoring that loading random classes at build time seems quite weird/unexpected, this does not work in my case because I'm integrating with some Java code that requires certain initializers to be run before other classes are loaded. Can I disable or otherwise circumvent this (and still use
aotAll())?Edit: disabling
checkClojureby settingnamespacesto the empty set reveals thatcompileClojurealso loads the classes. Because I kind of need compilation I don't know if there is any way around this issue. Maybe there is some way I can call the required initialization before classes are loaded?I found this issue. Whats interesting is that classes shouldn't be initialized by importing them with this being fixed, so I guess the class loading is happening due to my functions accessing static fields of a class?
Seems I can run initialization code conditionally using
*compile-files*, which isn't great but works fine so far.Beta Was this translation helpful? Give feedback.
All reactions