If you want a use case where this is a problem, here's mine:

I want to run FindBugs for my Android project in Travis-CI.

The output of Travis-CI is:

• Pass / fail
• The build log

With the current FindBugs Gradle support, the information that ends up in the build log is:

> FindBugs rule violations were found. See the report at: file:///home/travis/build/walles/exactype/app/build/reports/findbugs/findbugs.xml

Complete example here: https://travis-ci.org/walles/exactype/builds/87751928

This is not very helpful for somebody just reading the build log, especially since the file referenced isn't even accessible after the build is done.

I would prefer if FindBugs could print information in the build log on what exactly it was that went wrong, so that the user can fix the things FindBugs complains about just by reading the build log and nothing else.

One way of achieving this could be to support FindBugs text format output to stdout.

Updated forum reference for the old topic: https://discuss.gradle.org/t/findbugs-text-report-doesnt-work/2332

And a new request for the same feature: https://discuss.gradle.org/t/no-console-output-option-for-findbugs-plugin/11974

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!

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.