[GRADLE-1560] Tooling API should provide info on default tasks Created: 17/May/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Kris De Volder Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

In the Gradle manual it mentions that scripts can define a list of default tasks:

http://www.gradle.org/current/docs/userguide/tutorial_using_tasks.html#sec:default_tasks

It would be useful to expose this through the tooling API. It could be used to

  • preselect those task when creating an initial launch configuration (currently just creates conf with no tasks selected)
  • providing a menu command to run the default tasks without having to open a launch config editor

 Comments   
Comment by Kris De Volder [ 23/Oct/14 ]

A request came in on the STS issue tracker to implement functionality that requires information about default tasks in Gradle STS tooling:

https://issuetracker.springsource.com/browse/STS-3942

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 11:58:38 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.