[GRADLE-1026] Support task visibility Created: 10/Jul/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: New Feature
Reporter: Chris Beams Assignee: Unassigned
Resolution: Won't Fix Votes: 6

Issue Links:
Related
Related to GRADLE-1047 Simplify output of gradle -t Resolved

 Description   

I understand this is already planned for, but I didn't see a JIRA to this effect.

Often tasks need to be declared, but just as an implementation detail of a particular .gradle file.

Using existing groovy modifiers such as 'private' to hide these tasks from a '-t' listing would be a big help to usability.

private task implementationDetail {
   ...
}

task referenceDocs(dependsOn: implementationDetail) {
   ...
}

For reasons of backward compatibility and simplicity, I imagine that no visibility modifier would signify 'public' visibility, and thus 'public' could be used but would be redundant. I doubt that there is any need for protected or package-private visibility anyway. protected could have the same visibility as private, perhaps.

 Comments   
Comment by rday [ 02/Dec/13 ]

I concur, would like to have a way to not show a bunch of internal tasks to the user by default in gradle tasks

Comment by Alex Boyko [ 21/Oct/14 ]

Is this resolved in Gradle 2.1 with this API addition: http://www.gradle.org/docs/current/javadoc/org/gradle/tooling/model/Launchable.html#isPublic() ?

Comment by Richard [ 07/Jan/15 ]

Yes this works thanks.

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