[GRADLE-1824] "tasks" task hides tasks intended for public execution Created: 11/Oct/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-2
Fix Version/s: None

Type: Improvement
Reporter: Blaine Simpson Assignee: Unassigned
Resolution: Won't Fix Votes: 1


 Description   

I have tons of tasks which are intended for both automatic-internal dependsOn execution as well as explicit external execution. Example:

task dualUsefulnessTask << {
    ...
}
dualUsefulnessTaks.description = "Try this task"
task extOnlyTask(dependsOn:dualUsefulnessTask) << {
    ...
}

"dualUsefulnessTask" can and should be executed by both "gradle dualUsefulnessTask" and "gradle extOnlyTask". But "gradle tasks" hides the "dualUsefulnessTask" which I purposefully have described for external usage. My users must run "gradle tasks --all", which I definitely do not want my users to run because I have about 50 really internal tasks that I do not want to bother my users with.

Seems repressive to assume that because a task is "depended on" that it would be user-friendly to hide that from the casual user. I am assigning a .description specifically because I want to advertise the task to my end users.

 Comments   
Comment by Alan Evans [ 12/Oct/16 ]

Assigning a group will show it:

dualUsefulnessTaks.group = 'Some group'

If you don't want to list it in a group, you can put other:

dualUsefulnessTaks.group = 'Other'

This will mean it is listed along with the other tasks, just like nothing depended on it.

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:05:20 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.