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
Currently the generation of fat jars by spring is huge. A very simple hello world gives more than 10MB in classes. If we can use that to reduce the fatjar sizes it would be very useful
The text was updated successfully, but these errors were encountered:
If there are no dynamic method invocations (reflection), you would use this for tree-shaking to reduce the size of your fat jars. You'd just have to change the HashSet operations from a union to an intersection or something.
I've heard that GraalVM does the same thing, so you might want to check that out.
Also, you may want to look into using OSGi to deploy a graph of jars by the maven coordinate. It's equivalent to a fat jar but doesn't increase build time. It can be as simple as using:
Currently the generation of fat jars by spring is huge. A very simple hello world gives more than 10MB in classes. If we can use that to reduce the fatjar sizes it would be very useful
The text was updated successfully, but these errors were encountered: