@GOOGLE_ANALYTICS@

@HTML_SIDEBAR@

# FindBugs™ - Find Bugs in Java Programs

This is the web page for FindBugs, a program which uses static analysis to look for bugs in Java code. It is free software, distributed under the terms of the Lesser GNU Public License. The name FindBugs™ and the FindBugs logo are trademarked by The University of Maryland. FindBugs has been downloaded more than a million times.

The current version of FindBugs is @VERSION@.

FindBugs requires JRE (or JDK) 1.5.0 or later to run. However, it can analyze programs compiled for any version of Java, from 1.0 to 1.7. Some classfiles compiled for Java 1.8 give FindBugs problems, the next major release of FindBugs will handle Java 1.8 classfiles.

The current version of FindBugs is @VERSION@, released on @RELEASE_DATE@. We are very interested in getting feedback on how to improve FindBugs. File bug reports on our sourceforge bug tracker

The current version of FindBugs may encounter errors when analyzing Java 1.8 bytecode, due to changes in the classfile format. After FindBugs 2.0.3 is released, work will start on the next major release of FindBugs, which will be able to analyze Java 1.8 (and will require Java 1.7 to compile and run).

Changes | Talks | Papers | Sponsors | Support

# FindBugs 2.0.3 Release

FindBugs 2.0.3 is intended to be a minor bug fix release over FindBugs 2.0.2. Although than some improvements to existing bug detectors and analysis engines, and a few new bug patterns, and some important bug fixes to the Eclipse plugin, no significant changes should be observed. Consult the Change log for more details.

Also check out http://code.google.com/p/findbugs/w/list for more information about some recent features/changes in FindBugs.

### Major changes in FindBugs 2.0 (from FindBugs 1.3.x)

- FindBugs Communal cloud
- checks for updated versions of FindBugs
- Powerful plugin capabilities
- new bug patterns, including new/improved support for Guava and JSR-305
- improved performance

## Ways to run FindBugs

Here are various ways to run FindBugs. For plugins not supported by the FindBugs team, check to see what version of FindBugs they provide; it might take a little while for the plugins to update to FindBugs 2.0.

Command line, ant, GUI
  Provided in FindBugs download
Eclipse
  Update site for Eclipse plugin: http://findbugs.cs.umd.edu/eclipse. Supported by the FindBugs project.
Maven
  http://mojo.codehaus.org/findbugs-maven-plugin/
Netbeans
  SQE: Software Quality Environment
Jenkins
  Jenkins FindBugs Plugin
Hudson
  HUDSON FindBugs Plugin
IntelliJ
  Several plugins, see http://code.google.com/p/findbugs/wiki/IntellijFindBugsPlugins for a description.

# New

- jFormatString library republished at http://code.google.com/p/j-format-string. This is the library we use for compile time checking of format strings. It is separately published to
- We're releasing FindBugs 2.0.3. Mostly small changes to address false positives, with one important fix to the Eclipse plugin to fix a problem that had prevented the plugin from running in some versions of Eclipse. Check the change log for more details.
- We've released FindBugs 2.0
- FindBugs communal cloud and Java web start links:. We have analyzed several large open source projects, and provide Java web start links to allow you to view the results. We'd be happy to work with projects to make the results available from a continuous build:

  - Sun's JDK 8
  - Eclipse 3.8
  - Apache Tomcat 7.0
  - IntelliJ IDEA
  - JBoss

# Experience with FindBugs

- Google FindBugs Fixit: Google has a tradition of engineering fixits, special days where they try to get all of their engineers focused on some specific problem or technique for improving the systems at Google. A fixit might work to improve web accessibility, internal testing, removing TODO's from internal software, etc.

  In 2009, Google held a global fixit for UMD's FindBugs tool a static analysis tool for finding coding mistakes in Java software. The focus of the fixit was to get feedback on the 4,000 highest confidence issues found by FindBugs at Google, and let Google engineers decide which issues, if any, needed fixing.

  More than 700 engineers ran FindBugs from dozens of offices. More than 250 of them entered more than 8,000 reviews of the issues. A review is a classification of an issue as must-fix, should-fix, mostly-harmless, not-a-bug, and several other categories. More than 75% of the reviews classified issues as must fix, should fix or I will fix. Many of the scariest issues received more than 10 reviews each.

  Engineers have already submitted changes that made more than 1,100 of the 3,800 issues go away. Engineers filed more than 1,700 bug reports, of which 600 have already been marked as fixed Work continues on addressing the issues raised by the fixit, and on supporting the integration of FindBugs into the software development process at Google.

  The fixit at Google showcased new capabilities of FindBugs that provide a cloud computing / social networking backdrop. Reviews of issues are immediately persisted into a central store, where they can be seen by other developers, and FindBugs is integrated into the internal Google tools for filing and viewing bug reports and for viewing the version control history of source files. For the Fixit, FindBugs was configured in a mode where engineers could not see reviews from other engineers until they had entered their own; after the fixit, the configuration will be changed to a more open configuration where engineers can see reviews from others without having to provide their own review first. These capabilities have all been contributed to UMD's open source FindBugs tool, although a fair bit of engineering remains to prepare the capabilities for general release and make sure they can integrate into systems outside of Google. The new capabilities are expected to be ready for general release in Fall 2009.

## Talks about FindBugs

- Mistakes That Matter, JavaOne, 2009
- Youtube video showing of demo of our 2.0 Eclipse plugin (5 minutes)
- Quicktime movie showing of demo of our new GUI to view some of the null pointer bugs in Eclipse (Big file warning: 23 Megabytes)
- JavaOne 2007 talk on Improving Software Quality Using Static Analysis
- Talk Bill Pugh gave at SD Best Practices, Sept 14th (more of a handle on tutorial about using FindBugs)
- Talk Bill Pugh gave at ITA Software and MIT, Sept 12th and 13th (more of a research focus)
- Video of talk Bill Pugh gave at Google, July 6th, 2006
- Java Posse podcast interview with Bill Pugh and Brian Goetz

## Papers about FindBugs

- Finding More Null Pointer Bugs, But Not Too Many, by David Hovemeyer, York College of Pennsylvania and William Pugh, Univ. of Maryland, 7th ACM SIGPLAN-SIGSOFT Workshop on Program Analysis for Software Tools and Engineering, June, 2007
- Evaluating Static Analysis Defect Warnings On Production Software, Nathaniel Ayewah and William Pugh, Univ. of Maryland, and J. David Morgenthaler, John Penix and YuQian Zhou, Google, Inc., 7th ACM SIGPLAN-SIGSOFT Workshop on Program Analysis for Software Tools and Engineering, June, 2007

# Contributors and Sponsors

The current development team consists of Bill Pugh and Andrey Loskutov.

The most recent funding for FindBugs comes from a Google Faculty Research Awards.

## Additional Support

Numerous people have made significant contributions to the FindBugs project, including founding work by David Hovemeyer and the web cloud infrastructure by Keith Lea.

YourKit is kindly supporting open source projects with its full-featured Java Profiler. YourKit, LLC is creator of innovative and intelligent tools for profiling Java and .NET applications. Take a look at YourKit's leading software products: YourKit Java Profiler and YourKit .NET Profiler.

The FindBugs project also uses FishEye and Clover, which are generously provided by Cenqua/Atlassian.

Additional financial support for the FindBugs project was provided by National Science Foundation grants ASC9720199 and CCR-0098162,

Any opinions, findings and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation (NSF).

@HTML_FOOTER@