[GRADLE-1593] Tooling API should provide a way to create tasks and execute them Created: 06/Jun/11 Updated: 10/Feb/17 Resolved: 10/Feb/17
|Reporter:||Kris De Volder||Assignee:||Unassigned|
Perhaps it is easiest to explain what I'm after with a simple use case.
Let's say that we'd like the IDE to provide a menu command to generate the gradle wrapper for a project.
We already have API to execute tasks defined by the user in their build script, but we don't have any way for the IDE to create its own tasks and execute them.
|Comment by Adam Murdoch [ 23/Jun/11 ]|
I think it might be better to expose a way for Eclipse to manage the version of Gradle to use for a project, rather than a way to create tasks. For example:
This way, we can change how this works behind the tooling API. For example, the wrapper is baked into the tooling API implementation, and so it could just generate the wrapper files without executing Gradle or any tasks.
|Comment by Szczepan Faber [ 10/Mar/12 ]|
Kris mentioned in the email that he no longer needs that feature that much.
|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 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.