[GRADLE-3427] Expose CompilerDaemon functionality to Plugin Authors Created: 05/Apr/16 Updated: 24/Jan/17 Resolved: 24/Jan/17
Known Prospective Users
JetBrains is interested in adding Kotlin support.
Grails probably needs the same feature for the "unsafe incremental compiler"
The Core Gradle Team is currently working on prioritizing this design work so we can figure out a realistic schedule for early integrations with the API.
|Comment by Kyle Moore [ 26/Apr/16 ]
Hi Gradle team.
I've spent a few days investigating a potential way in which a 3rd party implementation of AbstractDaemonCompiler could theoretically execute in a forked process.
Please have a look at this publicly-shared Google document and feel free to leave comments (or tell me why I'm crazy and this would never work ):
|Comment by Kyle Moore [ 09/Jun/16 ]
I updated the above linked document with a more general introduction and links to a class diagram. The execution flow is complex but hopefully the diagram makes some sense.
Thanks again for your interest in this and see you at summit in a few weeks,
|Comment by Kyle Moore [ 10/Jun/16 ]
One more note on this-
I created an experimental snapshot of my Gradle plugin for Gosu which includes an implementation of AbstractDaemonCompiler. And I also created very simple sample project which uses this snapshot and is pre-configured to use forking compilation. So it should be as simple as downloading this archive, unzipping and running $ ./gradlew clean test to see an example of the ClassNotFoundException at the heart of this issue.
|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:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!
|Comment by Kyle Moore [ 16/Nov/16 ]
Thanks for the message, @bmuschko.
Yes, this issue is still quite relevant to my plugin, as well as any other 3rd-party plugin author who needs to access the client/worker APIs.
In fact, I spoke about this issue with Pepper in-person yesterday at the Bay Area meetup. Pepper claimed that changes to expose the worker API are currently being code reviewed - which is great news!! I am looking forward to taking advantage of this great feature soon.
|Comment by Eric Wendelin [ 24/Jan/17 ]
Moving to https://github.com/gradle/gradle/issues/1239 — please track it's progress there.