Gradle Stop Daemon

• Gradle Stop Daemon App
• Gradle Bootrun Stop

I've tried experimenting with spawning a process from a gradle task to see if it was something specific to the ExecTask and using the below task without the daemon Ctrl-C does stop the task but leaves the child processes running (the finally block doesn't get called as the java process has been forcibly terminated, tried looking to see if there.

• If you wish to stop a Daemon process manually, you can either kill the process via your operating system task manager or run the gradle -stopcommand. The -stopswitch causes Gradle to request that all running Daemon processes, of the same Gradle version used to run the command, terminate themselves.
• Summary I would like to know how to kill every single gradle daemon and process running on a machine regardless of the version of gradle or the version of the daemon, but the '-kill' or '-stop' command will only stop those processes that match the same version of gradle.

• Status:Resolved
• Affects Version/s:None

I have been getting push-back from the development team over our new Gradle-based build, as it is an order of magnitude slower to build and launch the application than it was using the old IDE-based build.

I've tried experimenting with spawning a process from a gradle task to see if it was something specific to the ExecTask and using the below task without the daemon Ctrl-C does stop the task but leaves the child processes running (the finally block doesn't get called as the java process has been forcibly terminated, tried looking to see if there.

• If you wish to stop a Daemon process manually, you can either kill the process via your operating system task manager or run the gradle -stopcommand. The -stopswitch causes Gradle to request that all running Daemon processes, of the same Gradle version used to run the command, terminate themselves.
• Summary I would like to know how to kill every single gradle daemon and process running on a machine regardless of the version of gradle or the version of the daemon, but the '-kill' or '-stop' command will only stop those processes that match the same version of gradle.

• Status:Resolved
• Affects Version/s:None

I have been getting push-back from the development team over our new Gradle-based build, as it is an order of magnitude slower to build and launch the application than it was using the old IDE-based build.

Gradle Stop Daemon App

I investigated using the Gradle daemon to improve the situation, and this initially looked promising, but I have run into a problem. When I run tasks like build, clean, distTar, etc, the daemon process continues running in the background, and subsequent tasks run much more quickly.

However, when I use the 'Run' task to launch the application, and then stop the application via a control-c on the command line, or the 'stop' function in the IDE (IntelliJ IDEA), then the daemon process is killed, and the subsequent task is again very slow to start. How can I ensure the daemon continues to run even when the run task is ended?

Gradle Bootrun Stop