[GRADLE-1364] Pattern rules of subprojects missing at the TaskReport Created: 03/Feb/11  Updated: 03/Feb/17  Resolved: 03/Feb/17

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

Type: Bug
Reporter: Mathias Kalb Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

The TaskReportTask ("gradle tasks") only add the rules of the master project and not the rules of the subprojects.
But it is possible to use the pattern rules ("gradle cleanJar").

org.gradle.api.tasks.diagnostics.TaskReportTask
    public void generate(Project project) throws IOException {
        ...
        for (Rule rule : project.getTasks().getRules()) {
            renderer.addRule(rule);
        }
build.gradle
subprojects {
	apply plugin: 'java'
}

http://gradle.1045684.n5.nabble.com/Pattern-rules-for-tasks-td3358284.html

 Comments   
Comment by Mathias Kalb [ 01/Mar/13 ]

It still does not work with the version 1.4.

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 Mathias Kalb [ 03/Dec/16 ]

It still does not work with the version 3.2.1.

Comment by Benjamin Muschko [ 03/Feb/17 ]

Thanks for confirming the issue. I can see that it still happens with Gradle 3.3. I am not going to migrate the issue as there are little votes from the community for solving the problem. Please open an issue on GitHub if you think it's crucial to your workflow.

Generated at Wed Jun 30 11:53:41 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.