[GRADLE-26] Add reporting Created: 09/Apr/08  Updated: 24/Jan/17  Resolved: 24/Jan/17

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

Type: New Feature
Reporter: Hans Dockter Assignee: Unassigned
Resolution: Fixed Votes: 9

Issue Links:
dependent on GRADLE-554 Add checkstyle support Resolved
dependent on GRADLE-555 Add CodeNarc support Resolved


We want to add reporting for:

JUnit, Emma, Cobertura, JDepend, pmd, findbugs, checkstyle

Comment by william wong [ 19/Jan/10 ]

As per the findbugs' bug report (http://sourceforge.net/tracker/index.php?func=detail&aid=2908672&group_id=96405&atid=614693), its ant task is not scalable and may not be executable with big project.

It is because the current ant task implementation depends on 'edu.umd.cs.findbugs.FindBugs' class, which assumes a findbug installed and executes the findbugs via command line.

It will be nice if the further findbugs plugin directly depends on 'edu.umd.cs.findbugs.FindBugs2' class, which relaxes this assumption. The current maven-findbugs-plugin depends on 'edu.umd.cs.findbugs.FindBugs2' maybe it is a good starting point....

Comment by Hans Dockter [ 31/Jan/10 ]

Thanks for pointing this out.

Comment by Johannes Buehler [ 26/Jan/11 ]

At hackergarten we worked on the findbugs plugin. It is almost done. https://github.com/jonnybbb/gradle

Comment by Tomek Kaczanowski [ 27/Jan/11 ]

Johannes, please update the cookbook (http://docs.codehaus.org/display/GRADLE/Cookbook) once the plugin for findbugs (or any other cool stuff you are working on) is ready.

Comment by Hans Dockter [ 27/Jan/11 ]

@Johannes Excellent! Thanks.

Comment by Leonard Brünings [ 24/Mar/11 ]

@Johannes could you guide me to the correct location, I could not find the findbugs plugin.

@all is it planned to combine all checking tools in the code-quality plugin?

Comment by Johannes Buehler [ 26/Mar/11 ]

@Leonard The plugin is not yet merged back into the gradle master. I have to include a few findings from Adam and Peter. If you want to have a previous look the code is checked into https://github.com/jonnybbb/gradle

Comment by Luke Daley [ 18/Apr/13 ]

Can we close this?

Comment by Johannes Buehler [ 18/Apr/13 ]

Yes, you can close this one.

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 [ 24/Jan/17 ]

All those static code analysis tools are now support by Gradle through plugins.

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