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
grails create-app website results in a website.jar that is 146M
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
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.
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: