-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reduce footprint of production jar #345
Comments
Just an FYI… These are the artifacts generated by “./gradlew assemble” for a default generated app after using “grails create-app” using 6.2.2 for sixapp and 7.0.0-M1 for sevenapp.
|
Is this behavior not what you would expect? |
I didn't have an expectation of how much bigger or smaller the artifacts would be, so I generated the apps to get an idea. |
The size difference is most probably due to |
Asset Pipeline 5.0.5 brought back edge case developmentOnly dependencies which dramatically increased the size of the war. |
grails create-app website
results in awebsite.jar
that is146M
The premise of Micronaut is to not have a monolith app and by forcing it into Grails makes Grails more monolithic adding 13+ more dependencies (plus transitives) to a Grails application
Given the overwhelming lack of support for keeping Micronaut part of Grails, it should be removed or made optional.
The implications of keeping Micronaut in a production environment:
Furthermore, creating a Spring Boot app requires a couple of dependencies in build.gradle to get up and going. Why does the most basic grails-app start with 36?
We also need to explore dependency reduction. If a dependency is transitive on another dependency, why is it in
build.gradle
? It is going to be resolved either way.6.2.1 build.gradle
Results in a production jar with
173
jarsThe text was updated successfully, but these errors were encountered: