You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
haskell compile too much class file, it led to its big jar size.
clojure has a simple solution for this situation for reference.
it has pomegranate library(just like haskell hint library), it can be used to load clojure file in runtime to generate class dynamically. it also publish clj file as maven repository directrly.
in case we need the same physical class sometimes, it offer the aot mechanism to compile only little needed class file before script interpretion procecure.
the situation is:
export physical jar class implement used by java project
some library use refletion mechanism to load class, so the physical class file must exist.
the reference doc is: https://clojure.org/reference/compilation
The text was updated successfully, but these errors were encountered:
Hi, the tool to minimize the jar that has been used so far is proguard , you can use it directly or including the appropiate gradle plugin if you are already are using gradle to build the eta project.
haskell compile too much class file, it led to its big jar size.
clojure has a simple solution for this situation for reference.
it has pomegranate library(just like haskell hint library), it can be used to load clojure file in runtime to generate class dynamically. it also publish clj file as maven repository directrly.
in case we need the same physical class sometimes, it offer the aot mechanism to compile only little needed class file before script interpretion procecure.
the situation is:
export physical jar class implement used by java project
some library use refletion mechanism to load class, so the physical class file must exist.
the reference doc is:
https://clojure.org/reference/compilation
The text was updated successfully, but these errors were encountered: