全部博文(413)
分类: 项目管理
2011-08-17 08:11:31
This web page provides automatic distribution and updates for the Eclipse plugin for FindBugs.
Plugin requirementsThis plugin has primarily been tested with Eclipse 3.3 and 3.4 It should work with 3.x releases, but let us know if you have any problems. The plugin is not compatible with versions of Eclipse preceding 3.3. The plugin runs under Java 1.5/5.0, or newer.
Plugin installationIf you have previously installed a version of the FindBugs plugin prior to mid-May, 2006, then you should remove it first. Simply remove the de.tobject.findbugs_0.0.n directory from Eclipse's plugins directory.
To install the FindBugs plugin:
We provide update sites that allow you to automatically install FindBugs into Eclipse and also query and install updates. There are three different update sites
FindBugs Eclipse update sites
Only provides official releases of FindBugs.
Provides official releases and release candidates of FindBugs.
Provides the daily build of FindBugs. No testing other than that it compiles.
You can also manually
download the plugin from the following link:
.
Extract it in Eclipse's "plugins" subdirectory.
(So
Once the plugin is extracted, start Eclipse and choose
→ → . You should find a plugin called "FindBugs Plug-in" provided by "FindBugs Project".
Version 0.6
Copyright 2008 - 2010 Lars Vogel
02.06.2010
Revision History | ||
---|---|---|
Revision 0.1 | 18.03.2008 | Lars Vogel |
Created | ||
Revision 0.2 - 0.5 | 18.05.2008 - 03.08.2009 | Lars Vogel |
bugfixes and updates | ||
Revision 0.6 | 02.06.2010 | Lars Vogel |
updated to latest Findbugs version and Eclipse 3.6 |
Findbugs
This article will describe the usage of the Findbugs plugin for Eclipse. Article is based on Eclipse 3.6 (Helios).
Table of Contents
4. Questions and DiscussionFindbugs performs static analysis for the Java byte-code to identify software bugs. By providing early feedback about certain (potential) errors in the coding it helps the developer to quickly identify problems in his coding.
Use the to install Findbugs from the Findbugs update site .
After installing findbugs you can activate findbugs for your project via the properties of your project and select FindBugs -> Run FindBugs automatically.
To see the Findbugs errors, select Window->Show View -> Other. The Findbugs errors will be displayed in this view.
|
Before posting questions, please see the . If you have questions or find an error in this article please use the . I have created a short list how to create good questions which might also help you.
Findbugs Homepage
Join my Eclipse RCP Training to become an RCP Expert in 5 days (Training in German)
Introduction to Android Programming
Program in Java and compile to JavaScript and HTML
Create native applications in Java
Test your application
Put everything you have under distributed version control system
############################################################
Error Description
from:
This document lists the standard bug patterns reported by version 1.3.9.
SummaryDescription | Category |
---|---|
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Bad practice | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
DMI: Vacuous call to collections | Correctness |
Correctness | |
Dm: Futile attempt to change max pool size of ScheduledThreadPoolExecutor | Correctness |
Dm: Creation of ScheduledThreadPoolExecutor with zero core threads | Correctness |
Dm: Useless/vacuous call to EasyMock method | Correctness |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
IL: An apparent infinite recursive loop | Correctness |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
MF: Method defines a variable that obscures a field | Correctness |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
STI: Unneeded use of currentThread() call, to call interrupted() | Correctness |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Correctness | |
Experimental | |
Experimental | |
Internationalization | |
Malicious code vulnerability | |
Malicious code vulnerability | |