FindBugs looks for bug patterns in Java byte code. Its homepage is findbugs.sourceforge.net. Because it analyses compiled classes rather than source text, it can catch problems that a source level checker cannot see.
The tool is part of the analysis chain that feeds JcReport. Its findings are normalised into the shared format before the combined report is rendered.
Updating FindBugs within fawkeZ
- Update the FindBugs version in
config/ivy.xml. - If the report schema of FindBugs changed, adopt
src/xml/findbugs/findbugs.xsdand possibly the normaliser code. - Check the upstream bug collection schema for the changes that affect the normaliser.
Configuration notes
FindBugs enables all of its checkers by default, so the project configuration is an exclude list rather than an include list. The report task sets the search effort and the minimum warning level, which together decide how many findings reach the combined report.
The FAQ describes how errors and warnings are weighted when the quality percentage is calculated.