Thanks for reporting an issue for Grails framework, please review the task list below before submitting the
issue. Your issue report will be closed if the issue is incomplete and the below tasks not completed.
[ ] Example that reproduces the problem uploaded to Github
[X] Full description of the issue provided (see below)
Steps to Reproduce
The GrailsGradlePlugin.enableFileWatch() method currently brings in the micronaut-inject-groovy into the runtime configuration. It should only be included for developmentOnly. This occurs when you are building the Grails application into an executable JAR/WAR.
Backport the change from the 5.0 branch to 4.0.x so that the method is changed from:
Thanks for reporting an issue for Grails framework, please review the task list below before submitting the issue. Your issue report will be closed if the issue is incomplete and the below tasks not completed.
NOTE: If you are unsure about something and the issue is more of a question a better place to ask questions is on Stack Overflow (http://stackoverflow.com/tags/grails) or Slack (http://slack-signup.grails.org). DO NOT use the issue tracker to ask questions.
Task List
Steps to Reproduce
The GrailsGradlePlugin.enableFileWatch() method currently brings in the micronaut-inject-groovy into the runtime configuration. It should only be included for developmentOnly. This occurs when you are building the Grails application into an executable JAR/WAR.
Backport the change from the 5.0 branch to 4.0.x so that the method is changed from:
to:
Expected Behaviour
micronaut-inject-groovy should not be inside of a production WAR/JAR file.
Actual Behaviour
when you assemble a WAR file, the micronaut-inject-groovy jar is included in the WAR which slows everything down.
Environment Information
Example Application