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
The main app's build.gradle file would conditionally include the plugin based on development environment.
Developers could add their own dev and testing utils that could be successfully live reloaded with a custom hotswap agent or spring dev tools.
Issue: broken hotreloading migrating away from run-app
With Grails 6+, we are trying to move away from grails run-app as suggested and use the gradlew wrapper instead.
However, hotreloading of the plugin does not work with either custom hotswap agent or spring dev tools using the gradle wrapper or gradle directly.
Reimplement or gradle alternative?
Hot reloading was a handy side effect of whatever grails run-app was doing. Like to have that back.
Would it be worth reimplementing a stripped down version of run-app? If so where is the original src for that? Haven't found the right file in the repo yet.
Or can we achieve the same thing with gradle build scripts and project restructuring? (I would post what I've tried, but it is be a lot of variations with no luck and would be a boring read.)
The text was updated successfully, but these errors were encountered:
I can work around it with gradle somewhat. By using the --continuous flag on certain gradle tasks, I can get it to reload controllers of the plugin, but not plugin views in their entirety..
Hotswap agent is able to detect changes to the gsp classes, but it does not reload the corresponding html data file,
Issue description
Previous Behaviour: Grails 5
On grails 5, the grails run-app command allowed us to successfully hotreload a multi-project structure like this:
folder/
--main app (grails 5 app)
------grails-app
------build.gradle
------settings.gradle
--dev utils (grails 5 app plugin)
------grails-app
------build.gradle
------settings.gradle
The main app's build.gradle file would conditionally include the plugin based on development environment.
Developers could add their own dev and testing utils that could be successfully live reloaded with a custom hotswap agent or spring dev tools.
Issue: broken hotreloading migrating away from run-app
With Grails 6+, we are trying to move away from grails run-app as suggested and use the gradlew wrapper instead.
However, hotreloading of the plugin does not work with either custom hotswap agent or spring dev tools using the gradle wrapper or gradle directly.
Reimplement or gradle alternative?
Hot reloading was a handy side effect of whatever grails run-app was doing. Like to have that back.
Would it be worth reimplementing a stripped down version of run-app? If so where is the original src for that? Haven't found the right file in the repo yet.
Or can we achieve the same thing with gradle build scripts and project restructuring? (I would post what I've tried, but it is be a lot of variations with no luck and would be a boring read.)
The text was updated successfully, but these errors were encountered: