FindBugs Eclipse Plugin

Add this URL to your Eclipse Installation to reach this solution's update site.

Mars (4.5), Luna (4.4), Kepler (4.3), Juno (4.2, 3.8), Previous to Juno (<=4.1)

Learn more...
Solution Description

FindBugs (as a project) is dead, but development continues under a new name: SpotBugs.

To get latest greatest SpotBugs plugin for Eclipse 4.6 and 4.7, please go to SpotBugs Eclipse plugin.

This listing is still there for old Eclipse versions < 4.6.

Additional Details

Eclipse Versions: Mars (4.5), Luna (4.4), Kepler (4.3), Juno (4.2, 3.8), Previous to Juno (<=4.1)

Platform Support: Windows, Mac, Linux/GTK

Organization Name: The University of Maryland

Development Status: Production/Stable

Date Created: Sunday, December 27, 2009 - 10:29

License: LGPL

Date Updated: Wednesday, December 14, 2022 - 09:47

Submitted by: Andrey Loskutov

Date Ranking Installs Clickthroughs
July 2024 77/619 176 4
June 2024 66/681 528 16
May 2024 64/682 615 15
April 2024 54/687 756 10
March 2024 66/694 681 16
February 2024 75/687 485 17
January 2024 81/691 492 18
December 2023 61/671 628 6
November 2023 73/686 700 19
October 2023 86/673 519 18
September 2023 71/663 591 14
August 2023 65/673 617 10
View Data for all Listings

Marketplace Drag to Install Button

By adding the following code below to your website you will be able to add an install button for FindBugs Eclipse Plugin.

HTML Code:

Markdown Syntax:


Drag to your running Eclipse* workspace. *Requires Eclipse Marketplace Client

Reviews Add new review

The webpage nor update site are not accessible.

"No repository found at ..."

Findbugs has become ubiquitous in Java shops.

Not only is it is run on Java itself, it is used by small startups through large corporations.

It's free and effective. It won't find every bug, but the bugs it finds are all real bugs. EVERY Java shop should be running Findbugs.

Obviously some bugs can exist for years and never cause a problem. If Findbugs identifies thousands of issues, create a plan to identify the top priority defects. That is, the ones the cost the company the most money.

You use JUnit to test your code? You perform code reviews?
If yes, then here is the tool which will find test failures and review issues even before you build your application - just as you type. If not, here is the tool which (in few minutes) will give you the proof, that your code is not worth to be deployed at all, and a good reason to start testing your application and to review your code.

FindBugs works similar to the Java compiler: as soon as you hit CTRL+S, Eclipse will compile the code and start incremental bug analysis. FindBugs can find an amazing number of different bug patterns, which are sometimes hard to debug or to reproduce. FindBugs has a very small number of false positives. Even if you think that the code will never run in the highlighted issue, in many cases the tool open your eyes on "dirty" places in your code.

FindBugs is valuable for both beginner and experienced programmers. If you just start to write Java applications, the tool will help you to learn better programming practices by explaining you the reasons why the code should be written in a different way. FindBugs helps experienced developers to keep the code clean and to review other's code by simply running the analysis over the Java projects.

FindBugs uses unique bytecode scanning techniques to analyze compiled Java code. In most cases the critical and medium severity bugs found by FindBugs are real, serious programming errors, and not just coding style issues. This is the main differentiator to other similar tools like PMD and Checkstyle (both are source-code analyzer).

I cannot imagine to seriously develop Java software without FindBugs Eclipse plugin anymore. For those who knows Ant and Hudson: of course, they also have plugins for FindBugs, so that you can use same tool as in your IDE to analyze your software during automated tests.