[GRADLE-3083] Application plugin - Stopping a running application kills the Gradle daemon Created: 08/May/14  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 1


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 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?

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:39:28 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.