FindBugs is an open source program created by Bill Pugh and David Hovemeyer which looks for bugs in Java code.[1][2] It uses static analysis[1][3] to identify hundreds of different potential types of errors[1] in Java programs. Potential errors are classified in four ranks: (i) scariest, (ii) scary, (iii) troubling and (iv) of concern. This is a hint to the developer about their possible impact or severity.[4] FindBugs operates on Java bytecode,[3] rather than source code. The software is distributed as a stand-alone GUI application. There are also plug-ins available for Eclipse, NetBeans,[5] IntelliJ IDEA,[6][7][8] Gradle, Hudson[9] and Jenkins.[10]

Additional rules sets can be plugged in FindBugs to increase the set of checks performed.[11]

Contents  [hide]

• 1 See also
• 2 References
• 3 External links
• 4 Further reading
  

See also[edit]

• List of tools for static code analysis
  

References[edit]

• ^ Jump up to:a b c FindBugs, Part 1: Improve the quality of your code
• Jump up^ FindBugs, Part 2: Writing custom detectors
• ^ Jump up to:a b Static Code Analysis
• Jump up^ Markus, Sprunck. "Findbugs - Static Code Analysis of Java". Retrieved April 24, 2013.
• Jump up^ NetBeans plug-in (from 7.2 onwards)
• Jump up^ idea-findbugs plug-in
• Jump up^ FindBugs-IDEA - The FindBugs Plugin for IntelliJ IDEA
• Jump up^ QAPlug-FindBugs plug-in
• Jump up^ http://wiki.hudson-ci.org/display/HUDSON/FindBugs+Plugin
• Jump up^ https://wiki.jenkins-ci.org/display/JENKINS/FindBugs+Plugin
• Jump up^ http://fb-contrib.sourceforge.net/
  

External links[edit]

• FindBugs website
• Manual
• List of bug patterns
• fb-contrib: additional bug detectors for FindBugs
• FindBugs-IDEA - The FindBugs Plugin for IntelliJ IDEA
• Using Static Analysis For Software Defect Detection
• Defective Java: Mistakes that matter - Bill Pugh
  

Further reading[edit]

• FindBugs In Eclipse Tutorial