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
Occasionally I'll end up running Gradle's clean task while the dev server is running, causing the task to fail, and the dev server to break as some of its files have been deleted. Ideally, when the clean task is run, the dev server would be terminated.
I initially tried to implement this myself, however, it doesn't look like there's any good way to terminate a JavaExec task and I didn't want to get too deep in the weeds of alternate solutions.
The text was updated successfully, but these errors were encountered:
It's a good idea, but it's really not easy to implement. Simultaneously running Gradle tasks cannot interact directly with each other, which means we will have to use file watchers, similar to those with which we reload developed plugin after build. However, this creates a problem - the clean task must wait until the server is completely shut down.
I'll think about how it could be implemented
Occasionally I'll end up running Gradle's
clean
task while the dev server is running, causing the task to fail, and the dev server to break as some of its files have been deleted. Ideally, when the clean task is run, the dev server would be terminated.I initially tried to implement this myself, however, it doesn't look like there's any good way to terminate a
JavaExec
task and I didn't want to get too deep in the weeds of alternate solutions.The text was updated successfully, but these errors were encountered: