Add findbugs for Android.

git-svn-id: http://src.chromium.org/svn/trunk/deps/third_party/findbugs@163586 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
diff --git a/LICENSE b/LICENSE
new file mode 100644
index 0000000..fb83997
--- /dev/null
+++ b/LICENSE
@@ -0,0 +1,57 @@
+GNU LESSER GENERAL PUBLIC LICENSE
+
+Version 3, 29 June 2007
+
+Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>
+
+Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
+
+This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License, supplemented by the additional permissions listed below.
+
+0. Additional Definitions.
+As used herein, “this License” refers to version 3 of the GNU Lesser General Public License, and the “GNU GPL” refers to version 3 of the GNU General Public License.
+
+“The Library” refers to a covered work governed by this License, other than an Application or a Combined Work as defined below.
+
+An “Application” is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library. Defining a subclass of a class defined by the Library is deemed a mode of using an interface provided by the Library.
+
+A “Combined Work” is a work produced by combining or linking an Application with the Library. The particular version of the Library with which the Combined Work was made is also called the “Linked Version”.
+
+The “Minimal Corresponding Source” for a Combined Work means the Corresponding Source for the Combined Work, excluding any source code for portions of the Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version.
+
+The “Corresponding Application Code” for a Combined Work means the object code and/or source code for the Application, including any data and utility programs needed for reproducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work.
+
+1. Exception to Section 3 of the GNU GPL.
+You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL.
+
+2. Conveying Modified Versions.
+If you modify a copy of the Library, and, in your modifications, a facility refers to a function or data to be supplied by an Application that uses the facility (other than as an argument passed when the facility is invoked), then you may convey a copy of the modified version:
+
+a) under this License, provided that you make a good faith effort to ensure that, in the event an Application does not supply the function or data, the facility still operates, and performs whatever part of its purpose remains meaningful, or
+b) under the GNU GPL, with none of the additional permissions of this License applicable to that copy.
+3. Object Code Incorporating Material from Library Header Files.
+The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure layouts and accessors, or small macros, inline functions and templates (ten or fewer lines in length), you do both of the following:
+
+a) Give prominent notice with each copy of the object code that the Library is used in it and that the Library and its use are covered by this License.
+b) Accompany the object code with a copy of the GNU GPL and this license document.
+4. Combined Works.
+You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following:
+
+a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License.
+b) Accompany the Combined Work with a copy of the GNU GPL and this license document.
+c) For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document.
+d) Do one of the following:
+0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.
+1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version.
+e) Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the GNU GPL, and only to the extent that such information is necessary to install and execute a modified version of the Combined Work produced by recombining or relinking the Application with a modified version of the Linked Version. (If you use option 4d0, the Installation Information must accompany the Minimal Corresponding Source and Corresponding Application Code. If you use option 4d1, you must provide the Installation Information in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.)
+5. Combined Libraries.
+You may place library facilities that are a work based on the Library side by side in a single library together with other library facilities that are not Applications and are not covered by this License, and convey such a combined library under terms of your choice, if you do both of the following:
+
+a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities, conveyed under the terms of this License.
+b) Give prominent notice with the combined library that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.
+6. Revised Versions of the GNU Lesser General Public License.
+The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Library as you received it specifies that a certain numbered version of the GNU Lesser General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that published version or of any later version published by the Free Software Foundation. If the Library as you received it does not specify a version number of the GNU Lesser General Public License, you may choose any version of the GNU Lesser General Public License ever published by the Free Software Foundation.
+
+If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy's public statement of acceptance of any version is permanent authorization for you to choose that version for the Library.
diff --git a/README.chromium b/README.chromium
new file mode 100644
index 0000000..8a995b8
--- /dev/null
+++ b/README.chromium
@@ -0,0 +1,11 @@
+Name: FindBugs
+URL: http://findbugs.sourceforge.net/
+Description: FindBugs is a program to find bugs in Java programs.
+Version: 2.0
+Security Critical: no
+License: LGPL 3
+License File: LICENSE
+
+Local Modifications:
+- Changed "#! /bin/sh" to "#!/bin/sh" in shell scripts to pass check_perms.
+- Set the svn:exeuctable bit correctly on bin/findbugs.bat and bin/findbugs.ico.
diff --git a/README.txt b/README.txt
new file mode 100644
index 0000000..4ddbe73
--- /dev/null
+++ b/README.txt
@@ -0,0 +1,20 @@
+To get started, see doc/index.html and doc/manual/index.html
+
+The FindBugs source license is in the file LICENSE.txt
+
+Both the name FindBugs and the FindBugs bug mark are
+trademarked by the University of Maryland.
+
+The Apache BCEL license is in the file LICENSE-bcel.txt
+
+The ASM license is in the file LICENSE-ASM.txt
+
+The dom4j license is in the file LICENSE-dom4j.txt
+
+The AppleJavaExtensions license is in the file LICENSE-AppleJavaExtensions.txt
+
+The Docbook 4.2 XML DTD license is in the file LICENSE-docbook.txt
+
+The JSR-305 reference implementation license is in LICENSE-jsr305.txt
+
+The Jaxen license is in LICENSE-jaxen.txt
diff --git a/bin/addMessages b/bin/addMessages
new file mode 100755
index 0000000..8c71ac1
--- /dev/null
+++ b/bin/addMessages
@@ -0,0 +1,73 @@
+#!/bin/sh
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.AddMessages
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
diff --git a/bin/computeBugHistory b/bin/computeBugHistory
new file mode 100755
index 0000000..717584b
--- /dev/null
+++ b/bin/computeBugHistory
@@ -0,0 +1,78 @@
+#!/bin/sh
+
+# Merge a historical bug collection and a bug collection, producing an updated
+# historical bug collection
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.workflow.Update
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/bin/convertXmlToText b/bin/convertXmlToText
new file mode 100755
index 0000000..a03440b
--- /dev/null
+++ b/bin/convertXmlToText
@@ -0,0 +1,73 @@
+#!/bin/sh
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.PrintingBugReporter
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
diff --git a/bin/copyBuggySource b/bin/copyBuggySource
new file mode 100755
index 0000000..e0e65df
--- /dev/null
+++ b/bin/copyBuggySource
@@ -0,0 +1,75 @@
+#!/bin/sh
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.workflow.CopyBuggySource
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/bin/defectDensity b/bin/defectDensity
new file mode 100755
index 0000000..0be8e57
--- /dev/null
+++ b/bin/defectDensity
@@ -0,0 +1,77 @@
+#!/bin/sh
+
+# Generate a defect density table from a bug collection
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.workflow.DefectDensity
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/bin/deprecated/bugHistory b/bin/deprecated/bugHistory
new file mode 100755
index 0000000..8d1aa3a
--- /dev/null
+++ b/bin/deprecated/bugHistory
@@ -0,0 +1,75 @@
+#!/bin/sh
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.workflow.BugHistory
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/bin/deprecated/unionBugs b/bin/deprecated/unionBugs
new file mode 100755
index 0000000..ca39afb
--- /dev/null
+++ b/bin/deprecated/unionBugs
@@ -0,0 +1,78 @@
+#!/bin/sh
+
+# Create the union of two results files, preserving
+# annotations in both files in the result.
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.UnionResults
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/bin/deprecated/unionResults b/bin/deprecated/unionResults
new file mode 100755
index 0000000..4c677f8
--- /dev/null
+++ b/bin/deprecated/unionResults
@@ -0,0 +1,80 @@
+#!/bin/sh
+
+# Deprecated
+
+# Create the union of two results files, preserving
+# annotations in both files in the result.
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.workflow.UnionResults
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/bin/deprecated/updateBugs b/bin/deprecated/updateBugs
new file mode 100755
index 0000000..717584b
--- /dev/null
+++ b/bin/deprecated/updateBugs
@@ -0,0 +1,78 @@
+#!/bin/sh
+
+# Merge a historical bug collection and a bug collection, producing an updated
+# historical bug collection
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.workflow.Update
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/bin/experimental/backdateHistoryUsingSource b/bin/experimental/backdateHistoryUsingSource
new file mode 100755
index 0000000..578b2c5
--- /dev/null
+++ b/bin/experimental/backdateHistoryUsingSource
@@ -0,0 +1,75 @@
+#!/bin/sh
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.workflow.BackdateHistoryUsingSource
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/bin/experimental/churn b/bin/experimental/churn
new file mode 100755
index 0000000..c90ddd5
--- /dev/null
+++ b/bin/experimental/churn
@@ -0,0 +1,75 @@
+#!/bin/sh
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.workflow.Churn
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/bin/experimental/obfuscate b/bin/experimental/obfuscate
new file mode 100755
index 0000000..82a4910
--- /dev/null
+++ b/bin/experimental/obfuscate
@@ -0,0 +1,75 @@
+#!/bin/sh
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.workflow.ObfuscateBugs
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/bin/experimental/treemapVisualization b/bin/experimental/treemapVisualization
new file mode 100755
index 0000000..316376b
--- /dev/null
+++ b/bin/experimental/treemapVisualization
@@ -0,0 +1,75 @@
+#!/bin/sh
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.workflow.TreemapVisualization
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/bin/fb b/bin/fb
new file mode 100755
index 0000000..62a45e6
--- /dev/null
+++ b/bin/fb
@@ -0,0 +1,192 @@
+#!/bin/sh
+
+# Launch FindBugs from the command line.
+
+escape_arg() {
+	echo "$1" | sed -e "s,\\([\\\"' 	]\\),\\\\\\1,g"
+}
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+
+fb_appjar="$findbugs_home/lib/findbugs.jar"
+
+ShowHelpAndExit() {
+	fb_mainclass="edu.umd.cs.findbugs.ShowHelp"
+	fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+	exit 0
+}
+
+# Set defaults
+fb_mainclass="edu.umd.cs.findbugs.workflow.FB"
+user_jvmargs=''
+ea_arg=''
+debug_arg=''
+conservespace_arg=''
+workhard_arg=''
+user_props=''
+
+# Handle command line arguments.
+while [ $# -gt 0 ]; do
+	case $1 in
+	-textui)
+		fb_mainclass="edu.umd.cs.findbugs.FindBugs2"
+		;;
+
+	-jvmArgs)
+		shift
+		user_jvmargs="$1"
+		;;
+		
+	-ea)
+		ea_arg='-ea'
+		;;
+
+	-maxHeap)
+		shift
+		fb_maxheap="-Xmx$1m"
+		;;
+
+	-javahome)
+		shift
+		fb_javacmd="$1/bin/java"
+		;;
+
+	-debug)
+		debug_arg="-Dfindbugs.debug=true"
+		;;
+
+	-conserveSpace)
+		conservespace_arg="-Dfindbugs.conserveSpace=true"
+		;;
+
+	-property)
+		shift
+		user_props="-D$1 $user_props"
+		;;
+	
+	-D*=*)
+		user_props="$1 $user_props"
+		;;
+
+	-version)
+		fb_mainclass=edu.umd.cs.findbugs.Version
+		fb_appargs="-release"
+		while [ $# -gt 0 ]; do
+			shift
+		done
+		fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+		exit 0
+		;;
+
+	-help)
+		ShowHelpAndExit
+		;;
+
+	# All unrecognized arguments will be accumulated and
+	# passed to the application.
+	*)
+		fb_appargs="$fb_appargs `escape_arg "$1"`"
+		;;
+	esac
+
+	shift
+done
+
+fb_jvmargs="$user_jvmargs $debug_arg $conservespace_arg $workhard_arg $user_props $ea_arg"
+if [ $maxheap ]; then
+  fb_maxheap="-Xmx${maxheap}m"
+fi
+
+# Extra JVM args for MacOSX.
+if [ $fb_osname = "Darwin" ]; then
+	fb_jvmargs="$fb_jvmargs \
+		-Xdock:name=FindBugs -Xdock:icon=${findbugs_home}/lib/buggy.icns \
+		-Dapple.laf.useScreenMenuBar=true"
+fi
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/bin/fbwrap b/bin/fbwrap
new file mode 100755
index 0000000..4437a24
--- /dev/null
+++ b/bin/fbwrap
@@ -0,0 +1,84 @@
+#!/bin/sh
+
+# A convenient way to call the main() method of a class
+# in findbugs.jar.
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+if [ $# -eq 0 ]; then
+	echo "Usage: fbwrap <main class name> <args...>"
+	exit 1
+fi
+
+fb_mainclass="$1"
+shift
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/bin/filterBugs b/bin/filterBugs
new file mode 100755
index 0000000..5071f48
--- /dev/null
+++ b/bin/filterBugs
@@ -0,0 +1,78 @@
+#!/bin/sh
+
+# General purpose utility for filtering/transforming
+# bug collection and/or historical bug collections
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.workflow.Filter
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/bin/findbugs b/bin/findbugs
new file mode 100755
index 0000000..126c5e1
--- /dev/null
+++ b/bin/findbugs
@@ -0,0 +1,199 @@
+#!/bin/sh
+
+# Launch FindBugs from the command line.
+
+escape_arg() {
+	echo "$1" | sed -e "s,\\([\\\"' 	]\\),\\\\\\1,g"
+}
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_appjar="$findbugs_home/lib/findbugs.jar"
+
+ShowHelpAndExit() {
+	fb_mainclass="edu.umd.cs.findbugs.ShowHelp"
+	fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+	exit 0
+}
+
+# Set defaults
+fb_mainclass="edu.umd.cs.findbugs.LaunchAppropriateUI"
+user_jvmargs=''
+ea_arg=''
+debug_arg=''
+conservespace_arg=''
+workhard_arg=''
+user_props=''
+
+# Handle command line arguments.
+while [ $# -gt 0 ]; do
+	case $1 in
+	-gui)
+		# this is the default
+		;;
+
+	-gui1)
+		user_props="-Dfindbugs.launchUI=1 $user_props"
+		;;
+
+	-textui)
+		fb_mainclass="edu.umd.cs.findbugs.FindBugs2"
+		;;
+
+	-jvmArgs)
+		shift
+		user_jvmargs="$1"
+		;;
+		
+	-ea)
+		ea_arg='-ea'
+		;;
+
+	-maxHeap)
+		shift
+		fb_maxheap="-Xmx$1m"
+		;;
+
+	-javahome)
+		shift
+		fb_javacmd="$1/bin/java"
+		;;
+
+	-debug)
+		debug_arg="-Dfindbugs.debug=true"
+		;;
+
+	-conserveSpace)
+		conservespace_arg="-Dfindbugs.conserveSpace=true"
+		;;
+
+	-property)
+		shift
+		user_props="-D$1 $user_props"
+		;;
+	
+	-D*=*)
+		user_props="$1 $user_props"
+		;;
+
+	-version)
+		fb_mainclass=edu.umd.cs.findbugs.Version
+		fb_appargs="-release"
+		while [ $# -gt 0 ]; do
+			shift
+		done
+		fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+		exit 0
+		;;
+
+	-help)
+		ShowHelpAndExit
+		;;
+
+	# All unrecognized arguments will be accumulated and
+	# passed to the application.
+	*)
+		fb_appargs="$fb_appargs `escape_arg "$1"`"
+		;;
+	esac
+
+	shift
+done
+
+fb_jvmargs="$user_jvmargs $debug_arg $conservespace_arg $workhard_arg $user_props $ea_arg"
+if [ $maxheap ]; then
+  fb_maxheap="-Xmx${maxheap}m"
+fi
+
+# Extra JVM args for MacOSX.
+if [ $fb_osname = "Darwin" ]; then
+	fb_jvmargs="$fb_jvmargs \
+		-Xdock:name=FindBugs -Xdock:icon=${findbugs_home}/lib/buggy.icns \
+		-Dapple.laf.useScreenMenuBar=true"
+fi
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/bin/findbugs-csr b/bin/findbugs-csr
new file mode 100755
index 0000000..074a174
--- /dev/null
+++ b/bin/findbugs-csr
@@ -0,0 +1,76 @@
+#!/bin/sh
+
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.workflow.CloudSyncAndReport
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/bin/findbugs-dbStats b/bin/findbugs-dbStats
new file mode 100755
index 0000000..fa0c0cb
--- /dev/null
+++ b/bin/findbugs-dbStats
@@ -0,0 +1,76 @@
+#!/bin/sh
+
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.cloud.db.DBStats
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/bin/findbugs-msv b/bin/findbugs-msv
new file mode 100755
index 0000000..3fe11d7
--- /dev/null
+++ b/bin/findbugs-msv
@@ -0,0 +1,76 @@
+#!/bin/sh
+
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.workflow.MergeSummarizeAndView
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/bin/findbugs.bat b/bin/findbugs.bat
new file mode 100755
index 0000000..0cc4621
--- /dev/null
+++ b/bin/findbugs.bat
@@ -0,0 +1,240 @@
+@echo off

+:: Launch FindBugs on a Windows system.

+:: Adapted from scripts found at http://www.ericphelps.com/batch/

+:: This will only work on Windows NT or later!

+

+:: Don't affect environment outside of this invocation

+setlocal

+

+:: ----------------------------------------------------------------------

+:: Set up default values

+:: ----------------------------------------------------------------------

+set appjar=findbugs.jar

+set javahome=

+set launcher=java.exe

+set start=start "FindBugs"

+set jvmargs=

+set debugArg=

+set conserveSpaceArg=

+set workHardArg=

+set args=

+set javaProps=

+set maxheap=768

+

+REM default UI is gui2

+set launchUI=2

+

+:: Try finding the default FINDBUGS_HOME directory

+:: from the directory path of this script

+set default_findbugs_home=%~dp0..

+

+:: Honor JAVA_HOME environment variable if it is set

+if "%JAVA_HOME%"=="" goto nojavahome

+if not exist "%JAVA_HOME%\bin\javaw.exe" goto nojavahome

+set javahome=%JAVA_HOME%\bin\

+:nojavahome

+

+goto loop

+

+:: ----------------------------------------------------------------------

+:: Process command-line arguments

+:: ----------------------------------------------------------------------

+

+:shift2

+shift

+:shift1

+shift

+

+:loop

+

+:: Remove surrounding quotes from %1 and %2

+set firstArg=%~1

+set secondArg=%~2

+

+if "%firstArg%"=="" goto launch

+

+:: AddMessages

+if not "%firstArg%"=="-addMessages" goto notAddMessages

+set fb_mainclass=edu.umd.cs.findbugs.AddMessages

+goto shift1

+:notAddMessages

+

+:: computeBugHistory

+if not "%firstArg%"=="-computeBugHistory" goto notUpdate

+set fb_mainclass=edu.umd.cs.findbugs.workflow.Update

+goto shift1

+:notUpdate

+

+:: convertXmlToText

+if not "%firstArg%"=="-xmltotext" goto notXmlToText

+set fb_mainclass=edu.umd.cs.findbugs.PrintingBugReporter

+goto shift1

+:notXmlToText

+

+:: copyBuggySource

+if not "%firstArg%"=="-copyBS" goto notCopyBS

+set fb_mainclass=edu.umd.cs.findbugs.workflow.CopyBuggySource

+goto shift1

+:notCopyBS

+

+:: defectDensity

+if not "%firstArg%"=="-defectDensity" goto notDefectDensity

+set fb_mainclass=edu.umd.cs.findbugs.workflow.DefectDensity

+goto shift1

+:notDefectDensity

+

+:: filterBugs

+if not "%firstArg%"=="-filterBugs" goto notFilterBugs

+set fb_mainclass=edu.umd.cs.findbugs.workflow.Filter

+goto shift1

+:notFilterBugs

+

+:: listBugDatabaseInfo

+if not "%firstArg%"=="-listBugDatabaseInfo" goto notListBugDatabaseInfo

+set fb_mainclass=edu.umd.cs.findbugs.workflow.ListBugDatabaseInfo

+goto shift1

+:notListBugDatabaseInfo

+

+:: mineBugHistory

+if not "%firstArg%"=="-mineBugHistory" goto notMineBugHistory

+set fb_mainclass=edu.umd.cs.findbugs.workflow.MineBugHistory

+goto shift1

+:notMineBugHistory

+

+:: printAppVersion

+if not "%firstArg%"=="-printAppVersion" goto notPrintAppVersion

+set fb_mainclass=edu.umd.cs.findbugs.workflow.PrintAppVersion

+goto shift1

+:notPrintAppVersion

+

+:: printClass

+if not "%firstArg%"=="-printClass" goto notPrintClass

+set fb_mainclass=edu.umd.cs.findbugs.workflow.PrintClass

+goto shift1

+:notPrintClass

+

+:: rejarForAnalysis

+if not "%firstArg%"=="-rejar" goto notRejar

+set fb_mainclass=edu.umd.cs.findbugs.workflow.RejarClassesForAnalysis

+goto shift1

+:notRejar

+

+:: setBugDatabaseInfo

+if not "%firstArg%"=="-setInfo" goto notSetBugDatabaseInfo

+set fb_mainclass=edu.umd.cs.findbugs.workflow.SetBugDatabaseInfo

+goto shift1

+:notSetBugDatabaseInfo

+

+:: unionBugs

+if not "%firstArg%"=="-unionBugs" goto notUnionBugs

+set fb_mainclass=edu.umd.cs.findbugs.workflow.UnionResults

+goto shift1

+:notUnionBugs

+

+:: xpathFind

+if not "%firstArg%"=="-xpathFind" goto notXPathFind

+set fb_mainclass=edu.umd.cs.findbugs.workflow.XPathFind

+goto shift1

+:notXPathFind

+

+if not "%firstArg%"=="-gui" goto notGui

+set launchUI=2

+set launcher=javaw.exe

+goto shift1

+:notGui

+

+if not "%firstArg%"=="-gui1" goto notGui1

+set launchUI=1

+set javaProps=-Dfindbugs.launchUI=1 %javaProps%

+set launcher=javaw.exe

+goto shift1

+:notGui1

+

+if not "%firstArg%"=="-textui" goto notTextui

+set launchUI=0

+set launcher=java.exe

+set start=

+goto shift1

+:notTextui

+

+if not "%firstArg%"=="-debug" goto notDebug

+set launcher=java.exe

+set start=

+set debugArg=-Dfindbugs.debug=true

+goto shift1

+:notDebug

+

+if not "%firstArg%"=="-help" goto notHelp

+set launchUI=help

+set launcher=java.exe

+set start=

+goto shift1

+:notHelp

+

+if not "%firstArg%"=="-version" goto notVersion

+set launchUI=version

+set launcher=java.exe

+set start=

+goto shift1

+:notVersion

+

+if "%firstArg%"=="-home" set FINDBUGS_HOME=%secondArg%

+if "%firstArg%"=="-home" goto shift2

+

+if "%firstArg%"=="-jvmArgs" set jvmargs=%secondArg%

+if "%firstArg%"=="-jvmArgs" goto shift2

+

+if "%firstArg%"=="-maxHeap" set maxheap=%secondArg%

+if "%firstArg%"=="-maxHeap" goto shift2

+

+if "%firstArg%"=="-conserveSpace" set conserveSpaceArg=-Dfindbugs.conserveSpace=true

+if "%firstArg%"=="-conserveSpace" goto shift1

+

+if "%firstArg%"=="-workHard" set workHardArg=-Dfindbugs.workHard=true

+if "%firstArg%"=="-workHard" goto shift1

+

+if "%firstArg%"=="-javahome" set javahome=%secondArg%\bin\

+if "%firstArg%"=="-javahome" goto shift2

+

+if "%firstArg%"=="-property" set javaProps=-D%secondArg% %javaProps%

+if "%firstArg%"=="-property" goto shift2

+

+if "%firstArg%"=="" goto launch

+

+set args=%args% "%firstArg%"

+goto shift1

+

+:: ----------------------------------------------------------------------

+:: Launch FindBugs

+:: ----------------------------------------------------------------------

+:launch

+:: Make sure FINDBUGS_HOME is set.

+:: If it isn't, try using the default value based on the

+:: directory path of the invoked script.

+:: Note that this will fail miserably if the value of FINDBUGS_HOME

+:: has quote characters in it.

+if not "%FINDBUGS_HOME%"=="" goto checkHomeValid

+set FINDBUGS_HOME=%default_findbugs_home%

+

+:checkHomeValid

+if not exist "%FINDBUGS_HOME%\lib\%appjar%" goto homeNotSet

+

+:found_home

+:: Launch FindBugs!

+if "%fb_mainclass%"=="" goto runJar

+"%javahome%%launcher%" %debugArg% %conserveSpaceArg% %workHardArg% %javaProps% "-Dfindbugs.home=%FINDBUGS_HOME%" -Xmx%maxheap%m %jvmargs% "-Dfindbugs.launchUI=%launchUI%" -cp "%FINDBUGS_HOME%\lib\%appjar%" %fb_mainclass% %args%

+goto end

+:runjar

+%start% "%javahome%%launcher%" %debugArg% %conserveSpaceArg% %workHardArg% %javaProps% "-Dfindbugs.home=%FINDBUGS_HOME%" -Xmx%maxheap%m %jvmargs% "-Dfindbugs.launchUI=%launchUI%" -jar "%FINDBUGS_HOME%\lib\%appjar%" %args%

+goto end

+

+:: ----------------------------------------------------------------------

+:: Report that FINDBUGS_HOME is not set (and was not specified)

+:: ----------------------------------------------------------------------

+:homeNotSet

+echo Could not find FindBugs home directory.  There may be a problem

+echo with the FindBugs installation.  Try setting FINDBUGS_HOME, or

+echo re-installing.

+goto end

+

+:end

diff --git a/bin/findbugs.ico b/bin/findbugs.ico
new file mode 100644
index 0000000..834ff37
--- /dev/null
+++ b/bin/findbugs.ico
Binary files differ
diff --git a/bin/findbugs2 b/bin/findbugs2
new file mode 100755
index 0000000..441ee10
--- /dev/null
+++ b/bin/findbugs2
@@ -0,0 +1,177 @@
+#!/bin/sh
+
+#
+# Simplified findbugs startup script.
+# This is an experiment.
+#
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+# Default UI is GUI2
+fb_launchui="2"
+
+#
+# Stuff we're going to pass to the JVM as JVM arguments.
+#
+jvm_debug=""
+jvm_maxheap="-Xmx768m"
+jvm_ea=""
+jvm_conservespace=""
+jvm_user_props=""
+
+#
+# Process command line args until we hit one we don't recognize.
+#
+finishedArgs=false
+while [ $# -gt 0 ] && [ "$finishedArgs" = "false" ]; do
+
+	arg=$1
+
+	case $arg in
+		-textui)
+			shift
+			fb_launchui="0"
+			;;
+
+		-gui)
+			shift
+			fb_launchui="2"
+			;;
+
+		-gui1)
+			shift
+			fb_launchui="1"
+			;;
+
+		-maxHeap)
+			shift
+			jvm_maxheap="-Xmx$1m"
+			shift
+			;;
+
+		-ea)
+			shift
+			jvm_ea="-ea"
+			;;
+
+		-javahome)
+			shift
+			fb_javacmd="$1/bin/java"
+			shift
+			;;
+
+		-debug)
+			shift
+			jvm_debug="-Dfindbugs.debug=true"
+			;;
+
+		-conserveSpace)
+			shift
+			jvm_conservespace="-Dfindbugs.conserveSpace=true"
+			;;
+
+		-property)
+			shift
+			jvm_user_props="-D$1 $jvm_user_props"
+			shift
+			;;
+	
+		-D*=*)
+			jvm_user_props="$1 $user_props"
+			shift
+			;;
+
+		-version)
+			shift
+			fb_launchui="version"
+			;;
+
+		-help)
+			shift
+			fb_launchui="help"
+			;;
+
+		# All arguments starting from the first unrecognized arguments
+		# are passed on to the Java app.
+		*)
+			finishedArgs=true
+			;;
+	esac
+
+done
+
+# Extra JVM args for MacOSX.
+if [ $fb_osname = "Darwin" ]; then
+	fb_jvmargs="$fb_jvmargs \
+		-Xdock:name=FindBugs -Xdock:icon=${findbugs_home}/lib/buggy.icns \
+		-Dapple.laf.useScreenMenuBar=true"
+fi
+
+#
+# Launch JVM
+#
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home" \
+	$jvm_debug $jvm_maxheap $jvm_ea $jvm_conservespace $jvm_user_props \
+	-Dfindbugs.launchUI=$fb_launchui \
+	-jar $findbugs_home/lib/findbugs.jar \
+	${@:+"$@"}
diff --git a/bin/listBugDatabaseInfo b/bin/listBugDatabaseInfo
new file mode 100755
index 0000000..da04ab2
--- /dev/null
+++ b/bin/listBugDatabaseInfo
@@ -0,0 +1,75 @@
+#!/bin/sh
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.workflow.ListBugDatabaseInfo
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/bin/mineBugHistory b/bin/mineBugHistory
new file mode 100755
index 0000000..fd4cbbf
--- /dev/null
+++ b/bin/mineBugHistory
@@ -0,0 +1,73 @@
+#!/bin/sh
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.workflow.MineBugHistory
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
diff --git a/bin/printAppVersion b/bin/printAppVersion
new file mode 100755
index 0000000..a0efd62
--- /dev/null
+++ b/bin/printAppVersion
@@ -0,0 +1,75 @@
+#!/bin/sh
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.workflow.PrintAppVersion
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/bin/printClass b/bin/printClass
new file mode 100755
index 0000000..6fb6c82
--- /dev/null
+++ b/bin/printClass
@@ -0,0 +1,73 @@
+#!/bin/sh
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.visitclass.PrintClass
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
diff --git a/bin/rejarForAnalysis b/bin/rejarForAnalysis
new file mode 100755
index 0000000..207fcd2
--- /dev/null
+++ b/bin/rejarForAnalysis
@@ -0,0 +1,75 @@
+#!/bin/sh
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.workflow.RejarClassesForAnalysis
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/bin/setBugDatabaseInfo b/bin/setBugDatabaseInfo
new file mode 100755
index 0000000..c50c9bf
--- /dev/null
+++ b/bin/setBugDatabaseInfo
@@ -0,0 +1,75 @@
+#!/bin/sh
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.workflow.SetBugDatabaseInfo
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/bin/unionBugs b/bin/unionBugs
new file mode 100755
index 0000000..4c677f8
--- /dev/null
+++ b/bin/unionBugs
@@ -0,0 +1,80 @@
+#!/bin/sh
+
+# Deprecated
+
+# Create the union of two results files, preserving
+# annotations in both files in the result.
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.workflow.UnionResults
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/bin/xpathFind b/bin/xpathFind
new file mode 100755
index 0000000..0f7cc21
--- /dev/null
+++ b/bin/xpathFind
@@ -0,0 +1,75 @@
+#!/bin/sh
+
+program="$0"
+
+# Follow symlinks until we get to the actual file.
+while [ -h "$program" ]; do
+	link=`ls -ld "$program"`
+	link=`expr "$link" : '.*-> \(.*\)'`
+	if [ "`expr "$link" : '/.*'`" = 0 ]; then
+		# Relative
+		dir=`dirname "$program"`
+		program="$dir/$link"
+	else
+		# Absolute
+		program="$link"
+	fi
+done
+
+# Assume findbugs home directory is the parent
+# of the directory containing the script (which should
+# normally be "$findbugs_home/bin").
+dir=`dirname "$program"`
+findbugs_home="$dir/.."
+
+# Handle FHS-compliant installations (e.g., Fink)
+if [ -d "$findbugs_home/share/findbugs" ]; then
+	findbugs_home="$findbugs_home/share/findbugs"
+fi
+
+# Make absolute
+findbugs_home=`cd "$findbugs_home" && pwd`
+
+fb_pathsep=':'
+
+# Handle cygwin, courtesy of Peter D. Stout
+fb_osname=`uname`
+if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+	findbugs_home=`cygpath --mixed "$findbugs_home"`
+	fb_pathsep=';'
+fi
+# Handle MKS, courtesy of Kelly O'Hair
+if [ "${fb_osname}" = "Windows_NT" ]; then
+	fb_pathsep=';'
+fi
+
+if [ ! -d "$findbugs_home" ]; then
+	echo "The path $findbugs_home,"
+	echo "which is where I think FindBugs is located,"
+	echo "does not seem to be a directory."
+	exit 1
+fi
+
+# Choose default java binary
+fb_javacmd=java
+if [ ! -z "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ]; then
+	if [ `expr "$fb_osname" : CYGWIN` -ne 0 ]; then
+		fb_javacmd=`cygpath --mixed "$JAVA_HOME"`/bin/java
+	else
+		fb_javacmd="$JAVA_HOME/bin/java"
+	fi
+fi
+
+fb_mainclass=edu.umd.cs.findbugs.xml.XPathFind
+
+fb_javacmd=${fb_javacmd:-"java"}
+fb_maxheap=${fb_maxheap:-"-Xmx768m"}
+fb_appjar=${fb_appjar:-"$findbugs_home/lib/findbugs.jar"}
+set -f
+#echo command: \
+exec "$fb_javacmd" \
+	-classpath "$fb_appjar$fb_pathsep$CLASSPATH" \
+	-Dfindbugs.home="$findbugs_home"\
+	$fb_maxheap $fb_jvmargs $fb_mainclass ${@:+"$@"} $fb_appargs
+
+# vim:ts=3
diff --git a/doc/AddingDetectors.txt b/doc/AddingDetectors.txt
new file mode 100644
index 0000000..131e690
--- /dev/null
+++ b/doc/AddingDetectors.txt
@@ -0,0 +1,237 @@
+Adding Detectors to FindBugs
+May 12, 2003
+Updated June 6, 2003 (detector meta-information, cleanups)
+
+===============
+1. Introduction
+===============
+
+FindBugs uses a plugin-based approach to adding detectors.
+This makes it easy for users to add their own detectors alongside
+the ones that come built in.
+
+Basic idea: FindBugs has some Jar files in a "plugins" directory.
+At startup, each of those jar files is checked for a "findbugs.xml"
+file.  That XML file registers instances of Detectors, as well
+as particular "bug patterns" that the detector reports.
+
+Additionally to the findbugs.xml, bugrank.txt and messages.xml files are
+required for each FindBugs detector plugin.
+
+At startup, FindBugs loads all plugin Jar files.  At analysis time,
+all detectors named in the findbugs.xml files from those plugins
+are instantiated and applied to analyzed class files.
+
+In order to format reported BugInstances as text for display,
+a messages file is loaded from the plugin.  In order to support multiple
+language translations, a locale search is performed in a manner
+similar to the handling of resource bundles.  For example, if the
+locale is "pt_BR", then the files
+
+  messages_pt_BR.xml
+  messages_pt.xml
+  messages.xml
+
+are tried, in that order.
+
+The "findbugs.xml" and "messages.xml" files used by the standard FindBugs
+bug pattern detectors (coreplugin.jar) can be found in the "etc" directory
+of the findbugs source distribution. Both files must be UTF-8 encoded.
+
+
+============================
+2. Example findbugs.xml file
+============================
+
+<DetectorPlugin>
+
+  <Detector class="org.foobar.findbugs.FindUnreleasedLocks" speed="slow" />
+  <Detector class="org.foobar.findbugs.ExperimentalDetector" speed="fast" disabled="true" />
+
+  <!-- More Detector elements would go here... -->
+
+  <BugPattern type="UBL_UNRELEASED_LOCK" abbrev="UL" category="MT_CORRECTNESS" />
+
+  <!-- More BugPattern elements would go here... -->
+
+</DetectorPlugin>
+
+
+======================================
+3. Meaning of elements in findbugs.xml
+======================================
+
+  <DetectorPlugin> a collection of <Detector> and <BugPattern> elements.
+  Each plugin Jar file can (and usually will) provide multiple detectors
+  and define multiple bug patterns.
+
+  <Detector> specifies a class which implements the edu.umd.cs.findbugs.Detector
+  interface and has a constructor that takes a single parameter of type
+  edu.umd.cs.findbugs.BugReporter.  This element has three possible attributes:
+
+    1. The required "class" attribute specifies the Detector class.
+
+    2. The optional "disabled" attribute, if set to "true", means
+       that by default, the detector will be disabled at runtime.
+       This is useful for detectors that aren't quite ready for prime time.
+
+    3. The required "speed" attribute supplies a value to be shown in the
+       "Settings->Configure Detectors" dialog.  It gives the user an idea of
+       how expensive the analysis will be to perform.  The value of this
+       attribute should be one of "fast", "moderate", or "slow".
+
+  <BugPattern> specifies a kind of bug that will be reported.
+  It has three required attributes:
+
+    1. "type" is a unique code identifying the bug.  Only one BugPattern
+       can have a a particular type.
+
+    2. "abbrev" is a short alphanumeric code for the bug.
+       Note that multiple BugPatterns can use the same abbreviation
+       if they are related.  (See the BugCode element in messages.xml).
+
+    3. "category" can be one of categories defined in the core plugin's messages.xml:
+
+       CORRECTNESS - code that was probably not what the developer intended
+       BAD_PRACTICE - violations of recommended and essential coding practice
+       STYLE - code that is confusing, anomalous, or written in a way that that leads itself to errors
+       MT_CORRECTNESS - multithreaded correctness issues
+       MALICIOUS_CODE - a potential vulnerability if exposed to malicious code
+       PERFORMANCE - a performance issue
+       I18N - internationalization and locale
+
+       or you may create your own category, in which case you should define
+       it in a <BugCategory> element in _your_ messages.xml file.
+
+============================
+4. Example messages.xml file
+============================
+
+<MessageCollection>
+
+  <Detector class="org.foobar.findbugs.FindUnreleasedLocks" >
+    <Details>
+      <![CDATA[
+        <p> This detector looks for JSR-166 locks that are not released on all paths
+        out of a method.  Because it performs dataflow analysis, it is fairly slow.
+      ]]>
+    </Details>
+  </Detector>
+
+  <!-- More Detector nodes would go here... -->
+
+  <BugPattern type="UBL_UNRELEASED_LOCK">
+    <ShortDescription>Lock not released on all paths out of method</ShortDescription>
+
+    <LongDescription>{1} does not release lock on all paths out of method</LongDescription>
+
+    <Details>
+      <![CDATA[
+        <p> A JSR-166 lock acquired in this method is not released on all paths
+        out of the method. This could result in a deadlock if another thread
+        tries to acquire the lock.  Generally, you should use a finally
+        block to ensure that acquired locks are always released.
+      ]]>
+    </Details>
+  </BugPattern>
+
+  <!-- More BugPattern nodes would go here... -->
+
+  <BugCode abbrev="UL">Unreleased locks</BugCode>
+
+  <!-- More BugCode nodes would go here... -->
+
+</MessageCollection>
+
+
+======================================
+5. Meaning of elements in messages.xml
+======================================
+
+  <MessageCollection> is the top level element
+
+  <BugCategory> elements optionally describe any categories you
+  may have created for your bug patterns. You can skip these if
+  you are using only the categories defined by the core plugin.
+
+    The <Description> child element has a brief (a word or three)
+    description of the category. The <Abbreviation> child element
+    is typically a single capital latter. The optional <Details>
+    child element may describe it in more detail (but no markup).
+
+  <Detector> holds meta-information about a Detector in the plugin.
+  The required "class" attribute specifies the Detector class.
+  Detector elements much have the following child elements:
+
+    The <Details> child element has a brief HTML description of the Detector.
+    It should have HTML markup that would be valid in a BODY element.
+    It should be specified in a CDATA section so that the HTML
+    tags are not misinterpreted as XML.
+
+  <BugPattern> holds all of the human-readable messages for the bug pattern
+  identified by the "type" attribute.  The type corresponds to the
+  type attribute of the BugPattern elements described in findbugs.xml.
+  BugPattern elements must have the following child elements:
+
+    <ShortDescription> this is used for when "View->Full Descriptions"
+    is turned off in the GUI, and it's also used as the title for
+    descriptions in the Details window.
+
+    <LongDescription> this is used for when "View->Full Descriptions"
+    is turned on in the GUI, and for output using the command line UI.
+    The placeholders in the long description ({0}, {1}, etc.)
+    refer to BugAnnotations attached to the BugInstances reported by
+    the detector for this bug pattern. You may also use constructs
+    like {1.name} or {1.returnType}.
+
+    <Details> this is the descriptive text to be used in the Details
+    window.  It consists of HTML markup to appear in the BODY element of an HTML
+    document.  It should be specified in a CDATA section so that the HTML
+    tags are not misinterpreted as XML.
+
+    <BugCode> is the text which describes the common characteristic of all
+    of the BugPatterns which share an abbreviation.  In the example above,
+    the abbreviation "UL" is for bugs in which a lock is not released.
+    The text of a BugCode element is shown for tree nodes in the GUI
+    which group bug instances by "bug type".
+
+======================================
+6. Meaning of elements in bugrank.txt
+======================================
+
+For the detailed and up to date information, please read the javadoc of the
+edu.umd.cs.findbugs.BugRanker class.
+
+============================================
+7. Using 3rd party libraries in the detector
+============================================
+
+FindBugs plugins may extend the default FindBugs classpath and use custom 3rd party
+libraries during the analysis. This libraries must be part of standard jar class path
+specified via "ClassPath" attribute in the META-INF/MANIFEST.MF file.
+
+======================================
+8. Adding detectors to Eclipse plugin
+======================================
+
+Since version 2.0.0 Eclipse plugin allows to configure or contribute custom detectors.
+
+7.1. It is possible to contribute custom detectors via standard Eclipse extensions mechanism.
+Please check the documentation of the "findBugsEclipsePlugin/schema/detectorPlugins.exsd"
+extension point how to update the plugin.xml. Existing FindBugs detector plugins can
+be easily "extended" to be full featured FindBugs & Eclipse detector plugins.
+Usually you only need to add META-INF/MANIFEST.MF and plugin.xml to the jar and
+update your build scripts to not to override the MANIFEST.MF during the build.
+
+7.2 It is possible to configure custom detectors via Eclipse workspace preferences.
+Go to "Window->Preferences->Java->FindBugs->Misc. Settings->Custom Detectors"
+and specify there locations of any additional plugin libraries.
+
+7.3 Plugins contributed via standard Eclipse extensions mechanism (see 7.1)
+may extend the default FindBugs classpath and use custom libraries during the analysis.
+This libraries must be part of standard Eclipse plugin dependencies specified via
+either "Require-Bundle" or "Bundle-ClassPath" attributes in the MANIFEST.MF file.
+In case custom detectors need access to this custom libraries at runtime, an
+extra line must be added to the MANIFEST.MF (without quotation marks):
+"Eclipse-RegisterBuddy: edu.umd.cs.findbugs.plugin.eclipse".
+
diff --git a/doc/Changes.html b/doc/Changes.html
new file mode 100644
index 0000000..440b153
--- /dev/null
+++ b/doc/Changes.html
@@ -0,0 +1,3550 @@
+<html>
+	<head>
+		<title>FindBugs Change Log</title>
+		<link rel="stylesheet" type="text/css" href="findbugs.css">
+		
+	</head>
+
+	<body>
+
+		<table width="100%">
+			<tr>
+
+				
+<td bgcolor="#b9b9fe" valign="top" align="left" width="20%"> 
+<table width="100%" cellspacing="0" border="0"> 
+<tr><td><a class="sidebar" href="index.html"><img src="umdFindbugs.png" alt="FindBugs"></a></td></tr> 
+
+<tr><td>&nbsp;</td></tr>
+
+<tr><td><b>Docs and Info</b></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="findbugs2.html">FindBugs 2.0</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="demo.html">Demo and data</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="users.html">Users and supporters</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="http://findbugs.blogspot.com/">FindBugs blog</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="factSheet.html">Fact sheet</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="manual/index.html">Manual</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="ja/manual/index.html">Manual(ja/&#26085;&#26412;&#35486;)</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="FAQ.html">FAQ</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="bugDescriptions.html">Bug descriptions</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="mailingLists.html">Mailing lists</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="publications.html">Documents and Publications</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="links.html">Links</a></font></td></tr> 
+
+<tr><td>&nbsp;</td></tr>
+
+<tr><td><a class="sidebar" href="downloads.html"><b>Downloads</b></a></td></tr> 
+
+<tr><td>&nbsp;</td></tr>
+
+<tr><td><a class="sidebar" href="http://www.cafeshops.com/findbugs"><b>FindBugs Swag</b></a></td></tr>
+
+<tr><td>&nbsp;</td></tr>
+
+<tr><td><b>Development</b></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="http://sourceforge.net/tracker/?group_id=96405">Open bugs</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="reportingBugs.html">Reporting bugs</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="contributing.html">Contributing</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="team.html">Dev team</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="api/index.html">API</a> <a class="sidebar" href="api/overview-summary.html">[no frames]</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="Changes.html">Change log</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="http://sourceforge.net/projects/findbugs">SF project page</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="http://code.google.com/p/findbugs/source/browse/">Browse source</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="http://code.google.com/p/findbugs/source/list">Latest code changes</a></font></td></tr> 
+</table> 
+</td>
+
+				<td align="left" valign="top">
+
+
+					<h1>FindBugs Change Log, Version 2.0.1</h1>
+
+                <ul>
+                    <li>New bug patterns; in some cases, bugs previous reported as other bug patterns are reported
+                        as instances of these new bug patterns in order to make it easier for developers to understand
+                        the bug reports</li>
+                    <ul>
+                        <li><a
+                            href="http://findbugs.sourceforge.net/bugDescriptions.html#PT_ABSOLUTE_PATH_TRAVERSAL">PT_ABSOLUTE_PATH_TRAVERSAL
+                        </a>
+                        <li><a
+                            href="http://findbugs.sourceforge.net/bugDescriptions.html#PT_RELATIVE_PATH_TRAVERSAL">PT_RELATIVE_PATH_TRAVERSAL
+                        </a>
+                        <li><a
+                            href="http://findbugs.sourceforge.net/bugDescriptions.html#NP_NONNULL_FIELD_NOT_INITIALIZED_IN_CONSTRUCTOR">NP_NONNULL_FIELD_NOT_INITIALIZED_IN_CONSTRUCTOR
+                        </a>
+                        <li><a
+                            href="http://findbugs.sourceforge.net/bugDescriptions.html#MS_SHOULD_BE_REFACTORED_TO_BE_FINAL">MS_SHOULD_BE_REFACTORED_TO_BE_FINAL
+                        </a>
+                        <li><a
+                            href="http://findbugs.sourceforge.net/bugDescriptions.html#BC_UNCONFIRMED_CAST_OF_RETURN_VALUE">BC_UNCONFIRMED_CAST_OF_RETURN_VALUE
+                        </a>
+                        <li><a
+                            href="http://findbugs.sourceforge.net/bugDescriptions.html#PT_ABSOLUTE_PATH_TRAVERSAL">PT_ABSOLUTE_PATH_TRAVERSAL
+                        </a>
+                        <li><a
+                            href="http://findbugs.sourceforge.net/bugDescriptions.html#TQ_COMPARING_VALUES_WITH_INCOMPATIBLE_TYPE_QUALIFIERS">TQ_COMPARING_VALUES_WITH_INCOMPATIBLE_TYPE_QUALIFIERS
+                        </a>
+                    </ul>
+                    <li>Changes to fix false negatives for the following bug patterns: <a
+                        href="http://findbugs.sourceforge.net/bugDescriptions.html#BC_UNCONFIRMED_CAST">BC_UNCONFIRMED_CAST</a>,
+                        <a href="http://findbugs.sourceforge.net/bugDescriptions.html#EC_BAD_ARRAY_COMPARE">EC_BAD_ARRAY_COMPARE</a>,
+                        <a href="http://findbugs.sourceforge.net/bugDescriptions.html#EQ_UNUSUAL">EQ_UNUSUAL</a>, <a
+                        href="http://findbugs.sourceforge.net/bugDescriptions.html#GC_UNRELATED_TYPES">GC_UNRELATED_TYPES</a>,
+                        and <a
+                        href="http://findbugs.sourceforge.net/bugDescriptions.html#NP_PARAMETER_MUST_BE_NONNULL_BUT_MARKED_AS_NULLABLE">NP_PARAMETER_MUST_BE_NONNULL_BUT_MARKED_AS_NULLABLE</a>.
+
+                    
+                    <li>Changes to fix false positions for the following bug patterns: <a
+                        href="http://findbugs.sourceforge.net/bugDescriptions.html#DMI_DOH">DMI_DOH</a>, <a
+                        href="http://findbugs.sourceforge.net/bugDescriptions.html#EC_UNRELATED_TYPES">EC_UNRELATED_TYPES</a>,
+                        and <a href="http://findbugs.sourceforge.net/bugDescriptions.html#SE_BAD_FIELD">SE_BAD_FIELD</a>.
+                    
+                </ul>
+
+                <h1>
+                        FindBugs Change Log, Version 2.0.0
+                    </h1>
+
+                                <h2> Changes since version 1.3.8</h2>
+					<ul>
+                         <li>New bug patterns; in some cases, bugs previous reported as other bug patterns are reported as instances
+                                          of these new bug patterns in order to make it easier for developers to understand the bug reports</li>
+                                          <ul>
+                                <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#BC_IMPOSSIBLE_DOWNCAST ">BC_IMPOSSIBLE_DOWNCAST </a>
+                                <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#BC_IMPOSSIBLE_DOWNCAST_OF_TOARRAY ">BC_IMPOSSIBLE_DOWNCAST_OF_TOARRAY </a>
+                                <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#EC_INCOMPATIBLE_ARRAY_COMPARE ">EC_INCOMPATIBLE_ARRAY_COMPARE </a>
+                                <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#JLM_JSR166_UTILCONCURRENT_MONITORENTER ">JLM_JSR166_UTILCONCURRENT_MONITORENTER </a>
+                                <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#LG_LOST_LOGGER_DUE_TO_WEAK_REFERENCE ">LG_LOST_LOGGER_DUE_TO_WEAK_REFERENCE </a>
+                                <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#NP_CLOSING_NULL ">NP_CLOSING_NULL </a>                              
+                                  <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#RC_REF_COMPARISON_BAD_PRACTICE ">RC_REF_COMPARISON_BAD_PRACTICE </a>                                <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#RC_REF_COMPARISON_BAD_PRACTICE_BOOLEAN ">RC_REF_COMPARISON_BAD_PRACTICE_BOOLEAN </a>                                <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#RV_RETURN_VALUE_OF_PUTIFABSENT_IGNORED ">RV_RETURN_VALUE_OF_PUTIFABSENT_IGNORED </a>                                <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#SIC_THREADLOCAL_DEADLY_EMBRACE ">SIC_THREADLOCAL_DEADLY_EMBRACE </a>                                <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#UR_UNINIT_READ_CALLED_FROM_SUPER_CONSTRUCTOR ">UR_UNINIT_READ_CALLED_FROM_SUPER_CONSTRUCTOR </a>                                <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#VA_FORMAT_STRING_EXPECTED_MESSAGE_FORMAT_SUPPLIED ">VA_FORMAT_STRING_EXPECTED_MESSAGE_FORMAT_SUPPLIED </a>
+                                          </ul>
+                                          <li>Providing a bug rank (1-20), and the ability to filter by bug rank. Eventually, 
+                                              it will be possible to specify your own rules for ranking bugs, but the procedure for doing so hasn't been specified yet.
+                                          <li>Fixed about <a href="https://sourceforge.net/search/index.php?group_id=96405&search_summary=1&search_details=1&type_of_search=artifact&group_artifact_id%5B%5D=614693&open_date_start=2009-03-16&open_date_end=2009-08-20&form_submit=Search">45 bugs filed</a> through SourceForge
+                                          <li>Various reclassifications and priority tweaks
+                                          <li>Added more bug annotations to a variety of bug reports.
+                                            This provides more context for understanding bug reports
+                                            (e.g., if the value in question was is the return value
+                                            of a method, the method is described as the source of
+                                            the value in a bug annotation). This also provide more
+                                            accurate tracking of issues across versions of the code
+                                            being analyzed, but has the downside that when comparing
+                                            results from FindBugs 1.3.8 and FindBugs 1.3.9 on the
+                                            same version of code being analyzed, 
+                                            FindBugs may think that mistakenly believe that the 
+                                            issue reported by 1.3.8 was fixed and a new issue was
+                                            introduced that was reported by FindBugs 1.3.9. While 
+                                            annoying, it would be unusual for more than a dozen 
+                                            issues per million
+                                            lines of codes to be mistracked. 
+                                           <li> Lots of internal changes moving towards FindBugs 2.0, but these
+                                           features are undocumented, not yet officially supported, and subject to
+                                           radical changes before FindBugs 2.0 is released.
+                                  
+             
+                            </ul>
+
+
+
+                                        <p> Changes since version 1.3.8</p>
+					<ul>
+                                          <li>New bug patterns; in some cases, bugs previous reported as other bug patterns are reported as instances
+                                          of these new bug patterns in order to make it easier for developers to understand the bug reports</li>
+                                          <ul>
+                                          <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#BC_IMPOSSIBLE_DOWNCAST ">BC_IMPOSSIBLE_DOWNCAST </a>
+                                <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#BC_IMPOSSIBLE_DOWNCAST_OF_TOARRAY ">BC_IMPOSSIBLE_DOWNCAST_OF_TOARRAY </a>
+                                <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#EC_INCOMPATIBLE_ARRAY_COMPARE ">EC_INCOMPATIBLE_ARRAY_COMPARE </a>
+                                <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#JLM_JSR166_UTILCONCURRENT_MONITORENTER ">JLM_JSR166_UTILCONCURRENT_MONITORENTER </a>
+                                <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#LG_LOST_LOGGER_DUE_TO_WEAK_REFERENCE ">LG_LOST_LOGGER_DUE_TO_WEAK_REFERENCE </a>
+                                <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#NP_CLOSING_NULL ">NP_CLOSING_NULL </a>                              
+                                  <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#RC_REF_COMPARISON_BAD_PRACTICE ">RC_REF_COMPARISON_BAD_PRACTICE </a>                                <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#RC_REF_COMPARISON_BAD_PRACTICE_BOOLEAN ">RC_REF_COMPARISON_BAD_PRACTICE_BOOLEAN </a>                                <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#RV_RETURN_VALUE_OF_PUTIFABSENT_IGNORED ">RV_RETURN_VALUE_OF_PUTIFABSENT_IGNORED </a>                                <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#SIC_THREADLOCAL_DEADLY_EMBRACE ">SIC_THREADLOCAL_DEADLY_EMBRACE </a>                                <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#UR_UNINIT_READ_CALLED_FROM_SUPER_CONSTRUCTOR ">UR_UNINIT_READ_CALLED_FROM_SUPER_CONSTRUCTOR </a>                                <li><a href="http://findbugs.sourceforge.net/bugDescriptions.html#VA_FORMAT_STRING_EXPECTED_MESSAGE_FORMAT_SUPPLIED ">VA_FORMAT_STRING_EXPECTED_MESSAGE_FORMAT_SUPPLIED </a>
+                                          </ul>
+                                          <li>Providing a bug rank (1-20), and the ability to filter by bug rank. Eventually, 
+                                              it will be possible to specify your own rules for ranking bugs, but the procedure for doing so hasn't been specified yet.
+                                          <li>Fixed about <a href="https://sourceforge.net/search/index.php?group_id=96405&search_summary=1&search_details=1&type_of_search=artifact&group_artifact_id%5B%5D=614693&open_date_start=2009-03-16&open_date_end=2009-08-20&form_submit=Search">45 bugs filed</a> through SourceForge
+                                          <li>Various reclassifications and priority tweaks
+                                          <li>Added more bug annotations to a variety of bug reports.
+                                            This provides more context for understanding bug reports
+                                            (e.g., if the value in question was is the return value
+                                            of a method, the method is described as the source of
+                                            the value in a bug annotation). This also provide more
+                                            accurate tracking of issues across versions of the code
+                                            being analyzed, but has the downside that when comparing
+                                            results from FindBugs 1.3.8 and FindBugs 1.3.9 on the
+                                            same version of code being analyzed, 
+                                            FindBugs may think that mistakenly believe that the 
+                                            issue reported by 1.3.8 was fixed and a new issue was
+                                            introduced that was reported by FindBugs 1.3.9. While 
+                                            annoying, it would be unusual for more than a dozen 
+                                            issues per million
+                                            lines of codes to be mistracked. 
+                                           <li> Lots of internal changes moving towards FindBugs 2.0, but these
+                                           features are undocumented, not yet officially supported, and subject to
+                                           radical changes before FindBugs 2.0 is released.
+                                  
+             
+             </ul>
+                                        <p> Changes since version 1.3.7</p>
+					<ul>
+                                          <li>Primarily another small bugfix release.</li>
+                                          <li>FindBugs base:</li>
+                                            <ul>
+                                              <li>New Reports:</li>
+                                              <ul>
+                                                <li>SF_SWITCH_NO_DEFAULT: missing default case in switch statement.</li>
+                                                <li>SF_DEAD_STORE_DUE_TO_SWITCH_FALLTHROUGH_TO_THROW: value ignored when switch fallthrough leads to
+                                                thrown exception.</li>
+                                                <li>INT_VACUOUS_BIT_OPERATION: bit operations that don't do any meaningful work.</li>
+                                                <li>FB_UNEXPECTED_WARNING: warning generated that conflicts with @NoWarning FindBugs annotation.</li>
+                                                <li>FB_MISSING_EXPECTED_WARNING: warning not generated despite presence of @ExpectedWarning FindBugs annotation.</li>
+                                                <li>NOISE category: intended for use in data mining experiments.</li>
+                                                <ul>
+                                                  <li>NOISE_NULL_DEREFERENCE: fake null point dereference warning.</li>
+                                                  <li>NOISE_METHOD_CALL:  fake method call warning.</li>
+                                                  <li>NOISE_FIELD_REFERENCE:  fake field dereference warning.</li>
+                                                  <li>NOISE_OPERATION:  fake operation warning.</li>
+                                                </ul>
+                                              </ul>
+                                              <li>Other:</li>
+                                              <ul>
+                                                <li>Garvin Leclaire has created a new Apache Maven repository for FindBugs at
+                                                <a href="http://code.google.com/p/findbugs/">the Google Code FindBugs SVN repository</a>.  (Thanks Garvin!)</li>
+                                              </ul>
+                                              <li>Fixes:</li>
+                                              <ul>
+                                                <li>[ 2317842 ] Highlighting broken in Windows</li>
+                                                <li>[ 2515908 ] check for oddness should track sign of argument</li>
+                                                <li>[ 2487936 ] &quot;L B GC&quot; false pos cast from Map.Entry.getKey() to Map.get()</li>
+                                                <li>[ 2528264 ] Ant tasks not compatible with Ant 1.7.1</li>
+                                                <li>[ 2539590 ] SF_SWITCH_FALLTHROUGH wrong message reported 	</li>
+                                                <li>[ 2020066 ] Bug history displayed in fancy-hist.xsl is incorrect</li>
+                                                <li>[ 2545098 ] Invalid character in analysis results file</li>
+                                                <li>[ 2492673 ] Plugin sites should specify &apos;requires Eclipse 3.3 or newer&apos;</li>
+                                                <li>[ 2588044 ] a tiny typing error</li>
+                                                <li>[ 2589048 ] Documentation for convertXmlToText insufficient</li>
+                                                <li>[ 2638739 ] NullPointerException when building</li>
+                                              </ul>
+                                              <li>Patches:</li>
+                                              <ul>
+                                                <li>[ 2538184 ] Make BugCollection implement Iterable&lt;BugInstance&gt; (thanks to Tomas Pollak)</li>
+                                                <li>[ 2249771 ] Add Maven2 Findbugs plugin link to the Links page (thanks to Garvin Leclaire)</li>
+                                                <li>[ 2609526 ] Japanese manual update (thanks to K. Hashimoto)</li>
+                                                <li>[ 2119482 ] CheckBcel checks for nonexistent classes (thanks to Jerry James)</li>
+                                              </ul>
+                                            </ul>
+                                          <li>FindBugs Eclipse plugin:</li>
+                                            <ul>
+                                              <li>Major feature enhancements (thanks to Andrey Loskutov).
+                                              See <a href="http://andrei.gmxhome.de/findbugs/index.html">this overview</a> for more information.</li>
+                                              <li>Major test improvements (thanks to Tomas Pollak).</li>
+                                              <li>Fixes:</li>
+                                              <ul>
+                                                <li>[ 2532365 ] Compiler warning</li>
+                                                <li>[ 2522989 ] Fix filter files selection</li>
+                                                <li>[ 2504068 ] NullPointerException</li>
+                                                <li>[ 2640849 ] NPE in Eclipse plugin 1.3.7 and Eclipse 3.5 M5</li>
+                                              </ul>
+                                              <li>Patches:</li>
+                                              <ul>
+                                                <li>[ 2143140 ] Unchecked conversion fixes for Eclipse plugin (thanks to Jerry James)
+                                              </ul>
+                                            </ul>
+                                          </ul>
+                                        </ul>
+
+                                        <p> Changes since version 1.3.6</p>
+					<ul>
+					<li>Overall, a small bugfix release. 
+					<li>New detection of accidental vacuous/useless calls to EasyMock methods,
+					and of generic signatures that proclaim the use of unhashable classes
+					in ways that require that they be hashed.
+					<li>Eliminate some false positives where we were warning about 
+					    a useless call (e.g., comparing two incompatible types for equality),
+					    but the only thing the code was doing with the result was 
+					    passing it to assertFalse.
+					<li>Japanese localization and manual by K.Hashimoto. (Thanks!)
+					<li>Added -exclude and -outputDir command line options to rejarForAnalysis
+					<li>Extended -adjustPriorities option to FindBugs analysis textui so that you
+						can modify the priorities of individual bug patterns as well as visitors,
+						and also completely suppress individual bug patterns or visitors. 
+						<ul>
+						<li> e.g., -adjustPriority MS_SHOULD_BE_FINAL=suppress,MS_PKGPROTECT=suppress,EI_EXPOSE_REP=suppress,EI_EXPOSE_REP2=suppress,PZLA_PREFER_ZERO_LENGTH_ARRAYS=raise
+						</ul>
+					</ul>
+					
+
+					<p> Changes since version 1.3.5</p>
+					<ul>
+					<li>Added fairly exhaustive static analysis
+					of uses of format strings, checking for missing or 
+					extra arguements, invalid format specifiers, 
+					or mismatched format specifiers and arguments (e.g,
+					passing a String value for a %d format specifier). 
+					The logic for doing so is derived from Sun's java.util.Formatter class,
+					and available separately from FindBugs as part of the
+					<a href="https://jformatstring.dev.java.net/">jFormatString</a> project.
+					
+					<li>More tuning of the unsatisfied obligation detector. Since this
+					detector is still rather noisy and an unfinished research project,
+					I've moved the generated issues to a new category: EXPERIMENTAL.
+					
+					<li>Added check for <a href="http://findbugs.sourceforge.net/bugDescriptions.html#BIT_ADD_OF_SIGNED_BYTE">BIT_ADD_OF_SIGNED_BYTE</a>; similar to <a href="http://findbugs.sourceforge.net/bugDescriptions.html#BIT_IOR_OF_SIGNED_BYTE">BIT_IOR_OF_SIGNED_BYTE</a>, except that 
+					addition is being used to combine shifted signed bytes.
+					
+					<li>Changed detection of EI_EXPOSE_REP2, so we only report it if  the value stored
+					is guaranteed to be the same value that was passed in as a parameter.
+					
+					<li>Added <a href="http://findbugs.sourceforge.net/bugDescriptions.html#EQ_CHECK_FOR_OPERAND_NOT_COMPATIBLE_WITH_THIS">EQ_CHECK_FOR_OPERAND_NOT_COMPATIBLE_WITH_THIS</a>, a warning when
+						an equals method checks to see if an operand is an instance of a class not
+							compatible with itself. For example, if the Foo class checks to see if the argument
+							is an instance of String. This is either a questionable design decision or a coding mistake.
+					<li>Added <a href="http://findbugs.sourceforge.net/bugDescriptions.html#DMI_INVOKING_HASHCODE_ON_ARRAY">DMI_INVOKING_HASHCODE_ON_ARRAY</a>, 
+						which checks for invoking <code>hashCode()</code> on an array, which returns a hash code that ignores the contents of the array.
+					<li>Added checks for using <code>x.removeAll(x)</code> to rather than <code>x.clear()</code>
+					to clear an array.
+					<li>Add checks for calls such as <code>x.contains(x)</code>, <code>x.remove(x)</code> and <code>x.containsAll(x)</code>.
+					<li>Improvements to Eclipse plugin (thanks to Andrey Loskutov):
+					<ul>
+					<li>Report separate markers for each occurrence of an issue that appears multiple times in a method
+					<li> fine tuning for reported markers: add only one marker for fields, add marker on right position 
+					<li>  link bugs selected in bug explorer view to the opened editor and vice versa 
+					<li> select bugs selected in editor ruler in the opened bug explorer view 
+					<li>  consistent abbreviations used in both bug explorer and bug details view 
+					<li> added "Expand All" button to the bug explorer view 
+					<li>  added "Go Into/Go Up" buttons to the bug explorer view 
+					<li>  added "Copy to clipboard" menu/functionality to the details view list widget 
+					<li> fix for CNF exception if loading the backup solution for broken browser widget 
+					
+					</ul></ul>
+					
+					
+
+					<p> Changes since version 1.3.4</p>
+					<ul>
+					<li>Analysis about 15% faster
+					<li><a href="http://sourceforge.net/tracker/?atid=614693&group_id=96405&func=browse&status=closed">38 bugs closed</a></li>
+					<li>New defect warnings:
+					<ul>
+					<li>calls to methods that always throw 
+						UnsupportedOperationException	 (DMI_UNSUPPORTED_METHOD)
+					<li>repeated conditional tests (e.g., 
+							<code>if (x &lt; 0 || x &lt; 0) ...</code>)
+						(RpC_REPEATED_CONDITIONAL_TEST)
+					<li>Complete rewrite of detector for format string problems.
+						More accurate, finds more problems, generates 
+							more descriptive reports, several different 
+								bug pattern
+						   (VA_FORMAT_STRING_EXTRA_ARGUMENTS_PASSED,
+						   VA_FORMAT_STRING_ILLEGAL,
+						   VA_FORMAT_STRING_MISSING_ARGUMENT,
+						   VA_FORMAT_STRING_BAD_ARGUMENT,
+						  VA_FORMAT_STRING_NO_PREVIOUS_ARGUMENT)
+
+					<li>Fairly complete implementation of JSR-305 custom type qualifier
+						analysis (no support for custom validators yet).
+						   (TQ_MAYBE_SOURCE_VALUE_REACHES_NEVER_SINK
+						   TQ_EXPLICIT_UNKNOWN_SOURCE_VALUE_REACHES_ALWAYS_SINK
+						   TQ_EXPLICIT_UNKNOWN_SOURCE_VALUE_REACHES_NEVER_SINK)
+					<li>New detector for unsatisfied obligations such forgetting to 
+						close a file (OBL_UNSATISFIED_OBLIGATION).
+					<li>Warning when a parameter is marked as nullable, but is
+						always dereferenced.
+						(NP_PARAMETER_MUST_BE_NONNULL_BUT_MARKED_AS_NULLABLE)
+					<lI>Separate warning for dereference the result of readLine (NP_DEREFERENCE_OF_READLINE_VALUE)
+					</ul>
+					<li>When XML is generated with messages, the project stats now 
+					include &lt;FileStat&gt; elements.
+					For each source file, this gives the path for the file,
+					the total number of warnings for that file, and a bugHash
+					for the file. While the instanceHash for a bug is intended 
+					to be version invariant (ignoring line numbers, etc), the
+					bugHash for a file is intended to reflect all the information
+					about the warnings in that file. The intended use case is that
+					if the bugHash for a file is the same in two analysis runs, 
+					then <em>nothing</em> has changed about any of the warnings
+					reported for that file between the two analysis runs.
+					<li>More merging of similar issues within a method. For example,
+						if the result of readLine() is dereferences multiple times
+						within a method, it will be reported as a single warning
+						with occurrences at multiple source lines.
+ 				</ul>
+					<p> Changes since version 1.3.3</p>
+
+					<ul>
+					  <li>FindBugs base
+					  <ul>
+					    <li>New Reports:</li>
+					    <ul>
+					      <li>EQ_OVERRIDING_EQUALS_NOT_SYMMETRIC:
+					      equals method overrides equals in superclass and may not be symmetric</li>
+					      <li>EQ_ALWAYS_TRUE:
+					      equals method always returns true</li>
+					      <li>EQ_ALWAYS_FALSE:
+					      equals method always returns false</li>
+					      <li>EQ_COMPARING_CLASS_NAMES:
+					      equals method compares class names rather than class objects</li>
+					      <li>EQ_UNUSUAL: Unusual equals method</li>
+					      <li>EQ_GETCLASS_AND_CLASS_CONSTANT:
+					      equals method fails for subtypes</li>
+					      <li>SE_READ_RESOLVE_IS_STATIC:
+					      The readResolve method must not be declared as a static method.</li>
+					      <li>SE_PRIVATE_READ_RESOLVE_NOT_INHERITED:
+					      private readResolve method not inherited by subclasses</li>
+					      <li>MSF_MUTABLE_SERVLET_FIELD: Mutable servlet field</li>
+					      <li>XSS_REQUEST_PARAMETER_TO_SEND_ERROR:
+					      Servlet reflected cross site scripting vulnerability</li>
+					      <li>SKIPPED_CLASS_TOO_BIG: Class too big for analysis</li>
+					    </ul>
+					    <li>Other:</li>
+					    <ul>
+					      <li>Value-number analysis now more space-efficient</li>
+					      <li>Enhancements to reduce memory overhead when
+					          analyzing very large classes</li>
+					      <li>Now skips very large classes that would otherwise
+					          take too much time and memory to analyze</li>
+					      <li>Infrastructure for tracking effectively-constant/
+					          effectively-final fields</li>
+					      <li>Added more cweids</li>
+					      <li>Enhanced taint tracking for taint-based detectors</li>
+					      <li>Ignore doomed calls to equals if result is used
+					          as an argument to assertFalse</li>
+					      <li>EQ_OVERRIDING_EQUALS_NOT_SYMMETRIC handles compareTo</li>
+					      <li>Priority tweak for ICAST_INTEGER_MULTIPLY_CAST_TO_LONG 
+					          (only low priority if multiplying by 1000)</li>
+					      <li>Improved tracking of fields across method calls</li>
+					    </ul>
+					    <li>Fixes:</li>
+					    <ul>
+					      <li>[ 1941450 ] DLS_DEAD_LOCAL_STORE not reported</li>
+					      <li>[ 1953323 ] Omitted break statement in SynchronizeAndNullCheckField</li>
+					      <li>[ 1942620 ] Source Directories selection dialog interface confusion (partial)</li>
+					      <li>[ 1948275 ] Unhelpful "Load of known null"</li>
+					      <li>[ 1933922 ] MWM error in findbugs</li>
+					      <li>[ 1934772 ] 1.3.3 appears to rely on JDK 1.6, JNLP still specifies 1.5</li>
+					      <li>[ 1933945 ] -loadbugs doesn't work</li>
+					      <li>Fixed problems for class names starting with '$'</li>
+					      <li>Fixed bugs and incomplete handling of annotations in
+					          VersionInsensitiveBugComparator</li>
+					    </ul>
+					    <li>Patches:</li>
+					    <ul>
+					      <li>[ 1955106 ] Javadoc fixes</li>
+					      <li>[ 1951930 ] Superfluous import statements (thanks to Jerry James)</li>
+					      <li>[ 1951907 ] Missing @Deprecated annotations (thanks to Jerry James)</li>
+					      <li>[ 1951876 ] Infonode Docking Windows compile fix (thanks to Jerry James)</li>
+					      <li>[ 1936055 ] bugfix for findbugs.de.comment not working (thanks to Peter Fokkinga)
+					    </ul>
+					  </ul>
+					  <li>FindBugs BlueJ plugin</li>
+					  <ul>
+					    <li>Updated to use FindBugs 1.3.4 (first new release since 1.1.3)</li>
+                      </ul>
+                    </ul>
+
+					<p> Changes since version 1.3.2</p>
+
+					<ul>
+					  <li>FindBugs base</li>
+					  <ul>
+					    <li>New Detectors:</li>
+					    <ul>
+					      <li>FieldItemSummary: Produces summary information
+                                    for what is stored into fields </li>
+					      <li>SynchronizeOnClassLiteralNotGetClass: Look for
+                                    code that synchronizes on the results of getClass
+                                    rather than on class literals</li>
+					      <li>SynchronizingOnContentsOfFieldToProtectField: This
+					          detector looks for code that seems to be
+					          synchronizing on a field in order to guard updates
+					          of that field </li>
+					    </ul>
+					    <li>New BugCode:</li>
+					    <ul>
+					      <li> HRS: HTTP Response splitting vulnerability </li>
+					      <li> WL: Possible locking on wrong object </li>
+					    </ul>
+					    <li>New Reports:</li>
+					    <ul>
+					      <li>DMI_CONSTANT_DB_PASSWORD:
+					          This code creates a database connect using a hard coded, constant password </li>
+					      <li>HRS_REQUEST_PARAMETER_TO_COOKIE:
+					          HTTP cookie formed from untrusted input </li>
+					      <li>HRS_REQUEST_PARAMETER_TO_HTTP_HEADER:
+					          HTTP parameter directly written to HTTP header output </li>
+					      <li>CN_IMPLEMENTS_CLONE_BUT_NOT_CLONEABLE:
+					          Class defines clone() but doesn't implement Cloneable </li>
+					      <li>DL_SYNCHRONIZATION_ON_BOXED_PRIMITIVE:
+					          Synchronization on boxed primitive could lead to deadlock </li>
+					      <li> DL_SYNCHRONIZATION_ON_BOOLEAN:
+					          Synchronization on Boolean could lead to deadlock </li>
+					      <li> ML_SYNC_ON_FIELD_TO_GUARD_CHANGING_THAT_FIELD:
+					          Synchronization on field in futile attempt to guard that field </li>
+					      <li> DLS_DEAD_LOCAL_STORE_IN_RETURN:
+					          Useless assignment in return statement </li>
+					      <li> WL_USING_GETCLASS_RATHER_THAN_CLASS_LITERAL:
+					          Synchronization on getClass rather than class literal </li>
+					    </ul>
+					    <li>Other:</li>
+					    <ul>
+					      <li>Many enhancements to cross-site scripting detector and its documentation</li>
+					      <li> Enhanced switch fall through handling </li>
+					      <li> Enhanced unread field handling (look for IF_ACMPEQ and IF_ACMPNE) </li>
+					      <li> Clarified documentation for @Nullable in manual </li>
+					      <li> Fewer DeadLocalStore false positives </li>
+					      <li> Fewer UnreadField false positives </li>
+					      <li> Fewer StaticCalendarDetector false positives </li>
+					      <li> Performance fix for slow file system IO e.g. Clearcase repositories (thanks, Andrei!) </li>
+					      <li> Other, general performance enhancements (thanks, Andrei!) </li>
+					      <li> Enhancements for using FindBugs scripts with MKS on Windows (thanks, Kelly O'Hair!) </li>
+					      <li> Noted in the manual that jsr305.jar must be present for annotations to compile </li>
+					      <li> Added and fine-tuned default-nullness annotations </li>
+					      <li> More CWE IDs added </li>
+					      <li> Check and warning for unexpected BCEL version in classpath </li>
+					    </ul>
+					    <li>Fixes:</li>
+					    <ul>
+					      <li>Bug fix to handling of local variable tables in BCEL</li>
+					      <li>Refined documentation for MTIA_SUSPECT_STRUTS_INSTANCE_FIELD</li>
+					      <li>[ 1927295 ] NPE when called on project root</li>
+					      <li>[ 1926405 ] Incorrect dead store warning</li>
+					      <li>[ 1926409 ] Incorrect redundant nullcheck warning</li>
+					      <li>[ 1926389 ] Wrong line number printed/highlighted in bug</li>
+					      <li>[ 1927040 ] typo in bug description</li>
+					      <li>[ 1926263 ] Minor glitch in HTML output</li>
+					      <li>[ 1926240 ] Minor error in standard options in manual</li>
+					      <li>[ 1926236 ] Minor bug in installation section of manual</li>
+					      <li>[ 1925539 ] ZIP is default file system code base</li>
+					      <li>[ 1894701 ] Livelock / memory leak in ObjectTypeFactory (thanks, Andrei!)</li>
+					      <li>[ 1867491 ] Doesn't reload annotations after code changes in IDE (thanks, Andrei!)</li>
+					      <li>[ 1921399 ] -project option not supported</li>
+					      <li>[ 1913834 ] "Dead" store to variable with method call</li>
+					      <li>[ 1917352 ] H B se:...field in serializable class</li>
+					      <li>[ 1911617 ] CloneIdiom relies on getNameConstantOperand for INSTANCEOF</li>
+					      <li>[ 1911620 ] False +: DLS predecrement before return</li>
+					      <li>[ 1871376 ] False negative: non-serializable Map field</li>
+					      <li>[ 1871051 ] non standard clone() method</li>
+					      <li>[ 1908854 ] Error in TestASM</li>
+					      <li>[ 1907539 ] 22 minor errors in bug checker documentation</li>
+					      <li>[ 1897323 ] EJB implementation class false positives</li>
+					      <li>[ 1899648 ] Crash on startup on Vista with Java 1.6.0_04</li>
+					    </ul>
+					    </ul>
+					  <li>FindBugs Eclipse plugin (change log by Andrey Loskutov)</li>
+					  <ul>
+					    <li> new feature: export basic FindBugs numbers for projects via File-&gt;Export-&gt;Java-&gt;BugCounts (Andrey Loskutov) </li>
+					    <li> new feature: jobs for different projects will be run in parallel per default if running on a
+                             multi-core PC ("fb.allowParallelBuild" system property not used anymore) (Andrey Loskutov) </li>
+					    <li> fixed performance slowdown in the multi-threaded build, caused by workspace operation locks during
+                             assigning marker attributes (Andrey Loskutov)</li>
+                       </ul>
+                    </ul>
+					
+					<p> Changes since version 1.3.1</p>
+
+					<ul>
+					  <li>FindBugs base</li>
+					  <ul>
+					    <li>New Bug Category:</li>
+					    <ul>
+					      <li>SECURITY (Abbrev: S), A use of untrusted input in
+					          a way that could create a remotely exploitable
+					          security vulnerability</li>
+					    </ul>
+					    <li>New Detectors:</li>
+					    <ul>
+					      <li>CrossSiteScripting: This detector looks for
+					          obvious/blatant cases of cross site scripting
+					          vulnerabilities</li>
+					    </ul>
+					    <li>New BugCode:</li>
+					    <ul>
+					      <li>XSS: Cross site scripting</li>
+					    </ul>
+					    <li>New Reports:</li>
+					    <ul>
+					      <li>XSS_REQUEST_PARAMETER_TO_SERVLET_WRITER: HTTP
+					          parameter directly written to Servlet output,
+					          giving XSS vulnerability</li>
+					      <li>XSS_REQUEST_PARAMETER_TO_JSP_WRITER: HTTP
+					          parameter directly written to JSP output, giving
+					          XSS vulnerability</li>
+					      <li>EQ_OTHER_USE_OBJECT: equals() method defined that
+					          doesn't override Object.equals(Object)</li>
+					      <li>EQ_OTHER_NO_OBJECT: equals() method inherits
+					          rather than overrides equals(Object)</li>
+					      <li>NP_NULL_ON_SOME_PATH_MIGHT_BE_INFEASIBLE:
+					          Possible null pointer dereference on path that
+					          might be infeasible</li>
+					    </ul>
+					    <li>Other:</li>
+					    <ul>
+					      <li>Added -noClassOk command-line parameter to
+					         command-line and ant interfaces; when -noClassOk
+					         is specified and no classfiles are given, FindBugs
+					         will print a warning message and output a well-
+					         formed file with no warnings</li>
+					      <li>Fewer false positives for null pointer bugs</li>
+					      <li>Suppress dead-local-store false positives in .jsp
+					          code</li>
+					      <li>Type fixes in warning messages</li>
+					      <li>Better warning message for
+					          NP_NULL_ON_SOME_PATH</li>
+					      <li>"WMI" bug code description renamed from "Wrong
+					          Map Iterator" to "Inefficient Map Iterator"</li>
+					    </ul>
+					    <li>Fixes:</li>
+					    <ul>
+					      <li>[ 1893048 ] FindBugs confused by a findbugs.xml file</li>
+					      <li>[ 1878528 ] XSL xforms don't support history features</li>
+					      <li>[ 1876584 ] two default.xsl flaws</li>
+					      <li>[ 1874856 ] Format string bug detector doesn't handle special operators</li>
+					      <li>[ 1872645 ] computeBugHistory - java.lang.IllegalArgumentException</li>
+					      <li>[ 1872237 ] Ant task fails when no .class files</li>
+					      <li>[ 1868670 ] Filters: include AND exclude don't allowed</li>
+					      <li>[ 1868666 ] check-for-oddness reported, but array length can never be negative</li>
+					      <li>[ 1866108 ] SetBugDatabaseInfoTask strips dir from output filename</li>
+					      <li>[ 1866021 ] MineBugHistoryTask strips dir of output filename</li>
+					      <li>[ 1865265 ] code doesn't handle StringBuffer.append([CII) right</li>
+					      <li>[ 1864793 ] Warning when casting a null reference compared to a String</li>
+					      <li>[ 1863376 ] Typo in manual chap 8: Filter Files</li>
+					      <li>[ 1862705 ] Transient fields that default to null</li>
+					      <li>[ 1842545 ] DLS on catch variable (with priority tweaking)</li>
+					      <li>[ 1816258 ] false positive BC_IMPOSSIBLE_CAST</li>
+					      <li>[ 1551732 ] Get erroneous DLS with while loop</li>
+					    </ul>
+					    </ul>
+					  <li>FindBugs Eclipse plugin (change log by Andrey Loskutov)</li>
+					  <ul>
+					    <li>new feature: added Bug explorer view (replacing Bug tree view), based on Common Navigator framework (Andrey Loskutov)</li>
+					    <li>bug 1873860 fixed: empty projects are no longer shown in Bug tree view  (Andrey Loskutov)</li>
+					    <li>new feature: bug counts decorators for projects, folders and files (has to be activated
+                            via Preferences -&gt; general -&gt; appearance -&gt; label decorations)(Andrey Loskutov)</li>
+					    <li>patch 1746499: better icons (Alessandro Nistico)</li>
+					    <li>patch 1893685: Find bug actions on change sets bug (Alessandro Nistico)</li>
+					    <li>fixed bug 1855384: Bug configuration is broken in Eclipse (Andrey Loskutov)</li>
+					    <li>refactored FindBugs properties page (Andrey Loskutov)</li>
+					    <li>refactored FindBugs worker/builder/run action (Andrey Loskutov)</li>
+					    <li>FB detects now only bugs from classes on project's classpath (no double work on
+                            duplicated class files) (Andrey Loskutov)</li>
+					    <li>fixed bug introduced by the bad patch for 1867951: FB cannot be executed incrementally
+                            on a folder of file (Andrey Loskutov)</li>
+					    <li>fixed job rule: now jobs for different projects may run in parallel if running on a
+                            multi-core PC and "fb.allowParallelBuild" system property is set to true (Andrey Loskutov)</li>
+					    <li>fixed FB auto-build not started if .fbprefs or .classpath was changed (Andrey Loskutov)</li>
+					    <li>fixed not reporting bugs on secondary types (classes defined in java files with
+ 					        different name) (Andrey Loskutov) </li>
+					  </ul>
+					</ul>
+
+					<p> Changes since version 1.3.0</p>
+					<ul>
+					<li>New Reports</li>
+					  <ul>
+					    <li>VA_FORMAT_STRING_ARG_MISMATCH:
+					        A format-string method with a variable number of arguments is called,
+                            but the number of arguments passed does not match with the number of
+                            % placeholders in the format string.  This is probably not what the
+                            author intended.
+                        <li>IO_APPENDING_TO_OBJECT_OUTPUT_STREAM:
+                            This code opens a file in append mode and that wraps the result in an object output stream. 
+                            This won't allow you to append to an existing object output stream stored in a file. If you want to be
+                            able to append to an object output stream, you need to keep the object output stream open.
+                            The only situation in which opening a file in append mode and the writing an object output stream
+                            could work is if on reading the file you plan to open it in random access mode and seek to the byte offset
+                            where the append started.
+                        <li>NP_BOOLEAN_RETURN_NULL:
+                            A method that returns either Boolean.TRUE, Boolean.FALSE or null is an accident waiting to happen.
+                            This method can be invoked as though it returned a value of type boolean, and
+                            the compiler will insert automatic unboxing of the Boolean value. If a null value is returned,
+                            this will result in a NullPointerException.
+					  </ul>
+					<li>Changes to Existing Reports</li>
+					<ul>
+					  <li>RV_DONT_JUST_NULL_CHECK_READLINE: CORRECTNESS -&gt; STYLE</li>
+					  <li>DMI_INVOKING_TOSTRING_ON_ARRAY: Long description mentions array name whenever possible</li>
+					</ul>
+					<li>Fixes:</li>
+					<ul>
+					<li>Updated manual to mention that Java 1.5 is now a requirement for running FindBugs
+					<li>Applied patch 1840206 fixing issue "Ant task does not work when presetdef is used" - thanks to phejl 
+					<li>Applied patch 1778690 fixing issue "Ant task: tolerate but complain about invalid auxClasspath" - thanks to David Schmidt
+					<li>Applied patch 1852125 adding a Chinese-language GUI bundle props file - thanks to fifi
+					<li>Applied patch 1845903 adding ability to load XML results with the Eclipse plugin - thanks to Alex Mont
+					<li>Fixed issue 1844671 - "FP for "reversed" null check in catch for stream close"
+					<li>Fixed issue 1836050 - "-onlyAnalyze broken"
+					<li>Fixed issue 1853011 - "Typo: Field names should start with aN lower case letter"
+					<li>Fixed issue 1844181 - "JNLP file does not contain all necessary JARs"
+					<li>Fixed issue 1840245 - "xxxException class does not derive from Exception"
+					<li>Fixed issue 1840277 - "[M D EC] Typo in bug documentation"
+					<li>Fixed issue 1782447 - "OutOfMemoryError if i activate Findbugs on my project"
+					<li>Fixed issue 1830576 - "[regression] keySet/entrySet false positive"
+					</ul>
+					<li>Other:</li>
+					<ul>
+					<li>New bug code: "IO" (for IO_APPENDING_TO_OBJECT_OUTPUT_STREAM)</li>
+					<li>Added "-onlyMostRecent" option for computeBugHistory script/ant task
+					<li>More explicit language in RV_RETURN_VALUE_IGNORED_BAD_PRACTICE messages
+					<li>Modified ResourceValueAnalysis to correctly identify null == X or null != X as a null check (for issue 1844671)
+					<li>Modified DMI_HARDCODED_ABSOLUTE_FILENAME logic in DumbMethodInvocations to ignore files from /etc or /dev and increase priority of files from /home
+					<li>Better bug details for infinite loop warnings
+					<li>Modified unread-fields detector to reduce false positives from reflective fields
+					<li>build.xml "classes" target now builds all sources in one step
+					</ul>
+					</ul>
+
+					<p> Changes since version 1.2.1</p>
+					<ul>
+					<li>New Detectors and Reports</li>
+					<ul>
+					  <li>SynchronizationOnSharedBuiltinConstant</li>
+					  <ul>
+					    <li>DL_SYNCHRONIZATION_ON_SHARED_CONSTANT:
+					        The code synchronizes on a shared primitive
+					        constant, such as an interned String.  Such
+					        constants are interned and shared across all other
+					        classes loaded by the JVM. Thus, this could be
+					        locking on something that other code might also be
+					        locking. This could result in very strange and hard
+					        to diagnose blocking and deadlock behavior. See
+					        <a href="http://www.javalobby.org/java/forums/t96352.html">http://www.javalobby.org/java/forums/t96352.html</a>
+					        and
+					        <a href="http://jira.codehaus.org/browse/JETTY-352">http://jira.codehaus.org/browse/JETTY-352</a>.
+					  </ul>
+					  <li>OverridingEqualsNotSymmetrical</li>
+					  <ul>
+					    <li>EQ_OVERRIDING_EQUALS_NOT_SYMMETRIC:
+					    Looks for equals methods that override equals
+					    methods in a superclass where the equivalence
+					    relationship might not be symmetrical.
+					  </ul>
+					  <li>CheckTypeQualifiers</li>
+					  <ul>
+					    <li>TQ_ALWAYS_VALUE_USED_WHERE_NEVER_REQUIRED:
+					    A value specified as carrying a type qualifier
+					    annotation is consumed in a location or locations
+					    requiring that the value not carry that annotation.
+					    More precisely, a value annotated with a type
+					    qualifier specifying when=ALWAYS is guaranteed to reach
+					    a use or uses where the same type qualifier specifies
+					    when=NEVER.
+					    </li>
+					    <li>TQ_NEVER_VALUE_USED_WHERE_ALWAYS_REQUIRED:
+					    A value specified as not carrying a type qualifier
+					    annotation is guaranteed to be consumed in a location
+					    or locations requiring that the value does carry that
+					    annotation.  More precisely, a value annotated with a
+					    type qualifier specifying when=NEVER is guaranteed to
+					    reach a use or uses where the same type qualifier
+					    specifies when=ALWAYS.
+					    </li>
+					    <li>TQ_MAYBE_SOURCE_VALUE_REACHES_ALWAYS_SINK:
+					    A value that might not carry a type qualifier
+					    annotation reaches a use which requires that
+					    annotation.
+					    </li>
+					    <li>TQ_MAYBE_SOURCE_VALUE_REACHES_NEVER_SINK:
+					    A value which might carry a type qualifier annotation
+					    reaches a use which forbids values carrying that
+					    annotation.
+					    </li>
+					  </ul>
+					</ul>
+					<li>New Reports (existing detectors)</li>
+					<ul>
+					  <li>FindHEmismatch</li>
+					  <ul>
+					    <li>EQ_DOESNT_OVERRIDE_EQUALS:
+					    This class extends a class that defines an equals
+					    method and adds fields, but doesn't define an equals
+					    method itself. Thus, equality on instances of this
+					    class will ignore the identity of the subclass and the
+					    added fields. Be sure this is what is intended, and
+					    that you don't need to override the equals method. Even
+					    if you don't need to override the equals method,
+					    consider overriding it anyway to document the fact that
+					    the equals method for the subclass just return the
+					    result of invoking super.equals(o).
+					    </li>
+					  </ul>
+					  <li>Naming
+					  <ul>
+					    <li>NM_WRONG_PACKAGE, NM_WRONG_PACKAGE_INTENTIONAL:
+					    The method in the subclass doesn't override a similar
+					    method in a superclass because the type of a parameter
+					    doesn't exactly match the type of the corresponding
+					    parameter in the superclass.
+					    </li>
+					    <li>NM_SAME_SIMPLE_NAME_AS_SUPERCLASS:
+					    This class has a simple name that is identical to that
+					    of its superclass, except that its superclass is in a
+					    different package (e.g., <code>alpha.Foo</code>
+					    extends <code>beta.Foo</code>).  This can be
+					    exceptionally confusing, create lots of situations in
+					    which you have to look at import statements to resolve
+					    references and creates many opportunities to
+					    accidently define methods that do not override methods
+					    in their superclasses.
+					    </li>
+					    <li>NM_SAME_SIMPLE_NAME_AS_INTERFACE:
+					    This class/interface has a simple name that is
+					    identical to that of an implemented/extended 
+					    interface, except that the interface is in a different
+					    package (e.g., <code>alpha.Foo</code> extends
+					    <code>beta.Foo</code>).  This can be exceptionally
+					    confusing, create lots of situations in which you have
+					    to look at import statements to resolve references and
+					    creates many opportunities to accidently define methods
+					    that do not override methods in their superclasses.
+					    </li>
+					  </ul>
+					  <li>FindRefComparison</li>
+					  <ul>
+					    <li>EC_UNRELATED_TYPES_USING_POINTER_EQUALITY:
+					    This method uses using pointer equality to compare two
+					    references that seem to be of different types.  The
+					    result of this comparison will always be false at
+					    runtime.
+					    </li>
+					  </ul>
+					  <li>IncompatMask</li>
+					  <ul>
+					    <li>BIT_SIGNED_CHECK, BIT_SIGNED_CHECK_HIGH_BIT:
+					    This method compares an expression such as
+					    <tt>((event.detail &amp; SWT.SELECTED) &gt; 0)</tt>.  Using
+					    bit arithmetic and then comparing with the greater than
+					    operator can lead to unexpected results (of course
+					    depending on the value of SWT.SELECTED). If
+					    SWT.SELECTED is a negative number, this is a candidate
+					    for a bug. Even when SWT.SELECTED is not negative, it
+					    seems good practice to use '!= 0' instead of '&gt; 0'.
+					    </li>
+					  </ul>
+					  <li>LazyInit</li>
+					  <ul>
+					    <li>LI_LAZY_INIT_UPDATE_STATIC:
+					    This method contains an unsynchronized lazy
+					    initialization of a static field.  After the field is
+					    set, the object stored into that location is further
+					    accessed.  The setting of the field is visible to other
+					    threads as soon as it is set. If the further accesses in
+					    the method that set the field serve to initialize the
+					    object, then you have a <em>very serious</em>
+					    multithreading bug, unless something else prevents any
+					    other thread from accessing the stored object until it
+					    is fully initialized.
+					    </li>
+					  </ul>
+					  <li>FindDeadLocalStores</li>
+					  <ul>
+					    <li>DLS_DEAD_STORE_OF_CLASS_LITERAL:
+					    This instruction assigns a class literal to a variable
+					    and then never uses it.
+					    <a href="//java.sun.com/j2se/1.5.0/compatibility.html#literal">The behavior of this differs in Java 1.4 and in Java 5.</a>
+					    In Java 1.4 and earlier, a reference to
+					    <code>Foo.class</code> would force the static
+					    initializer for <code>Foo</code> to be executed, if it
+					    has not been executed already.  In Java 5 and later, it
+					    does not.  See Sun's
+					    <a href="//java.sun.com/j2se/1.5.0/compatibility.html#literal">article on Java SE compatibility</a>
+					    for more details and examples, and suggestions on how
+					    to force class initialization in Java 5.
+					    </li>
+					  </ul>
+					  <li>MethodReturnCheck</li>
+					  <ul>
+					    <li>RV_RETURN_VALUE_IGNORED_BAD_PRACTICE:
+					    This method returns a value that is not checked. The
+					    return value should be checked since it can indication
+					    an unusual or unexpected function execution. For
+					    example, the <code>File.delete()</code> method returns
+					    false if the file could not be successfully deleted
+					    (rather than throwing an Exception).  If you don't
+					    check the result, you won't notice if the method
+					    invocation signals unexpected behavior by returning an
+					    atypical return value.
+					    </li>
+					    <li>RV_EXCEPTION_NOT_THROWN:
+					    This code creates an exception (or error) object, but
+					    doesn't do anything with it.
+					    </li>
+					  </ul>
+					</ul>
+					<li>Changes to Existing Reports</li>
+					<ul>
+					  <li>NS_NON_SHORT_CIRCUIT: BAD_PRACTICE -&gt; STYLE</li>
+					  <li>NS_DANGEROUS_NON_SHORT_CIRCUIT: CORRECTNESS -&gt; STYLE</li>
+					  <li>RC_REF_COMPARISON: CORRECTNESS -&gt; BAD_PRACTICE</li>
+					</ul>
+					<li>GUI Changes</li>
+					<ul>
+					  <li>Added importing and exporting of bug filters</li>
+					  <li>Better handling of failed analysis runs</li>
+					  <li>Added "-look" parameter for selecting look-and-feel</li>
+					  <li>Fixed incorrect package filtering</li>
+					  <li>Fixed issue where "synchronized" was not syntax-highlighted</li>
+					</ul>
+					<li>Ant-task Changes</li>
+					<ul>
+					  <li>Refactored common ant-task code to AbstractFindBugsTask</li>
+					  <li>Added tasks for computeBugHistory, convertXmlToText, filterBugs, mineBugHistory, setBugDatabaseInfo</li>
+					</ul>
+					<li>Manual</li>
+					<ul>
+					  <li>Updates to GUI section, including new screenshots</li>
+					  <li>Added description of rejarForAnalysis</li>
+					  <li>Revamp of data-mining section</li>
+					</ul>
+					<li>Other Major</li>
+					<ul>
+					  <li>Internal restructuring for lower memory overhead</li>
+					</ul>
+					<li>Other Minor</li>
+					<ul>
+					  <li>Fixed typo: was STCAL_STATIC_SIMPLE_DATA_FORMAT_INSTANCE now STCAL_STATIC_SIMPLE_DATE_FORMAT_INSTANCE</li>
+					  <li>-outputFile parameter became -output</li>
+					  <li>More sensitivity and specificity inLazyInit detector</li>
+					  <li>More sensitivity and specificity in Naming detector</li>
+					  <li>More sensitivity and specificity in UnreadFields detector</li>
+					  <li>More sensitivity in FindNullDeref detector</li>
+					  <li>More sensitivity in FindBadCast2 detector</li>
+					  <li>More specificity in FindReturnRef detector</li>
+					  <li>Many other tweaks and bug fixes</li>
+					</ul>
+					</ul>
+
+					<p> Changes since version 1.2.0</p>
+					<ul>
+					<li>Bug fixes:
+					<ul>
+					<li><a href="http://fisheye2.cenqua.com/changelog/findbugs/?cs=8219">Fix</a> <a href="http://sourceforge.net/tracker/index.php?func=detail&aid=1726946&group_id=96405&atid=614693">bug</a> with detectors that were requested to be disabled but were enabled due to requirements of other detectors.</li>
+					<li>Fix bugs in incremental analysis within Eclipse plugin</li>
+					<li>Fix some analysis errors</li>
+					<li>Fix some threading bugs in GUI2</li>
+					<li>Report version as version when it was compiled, not when it was run</li>
+					<li>Copy analysis time stamp when filtering or transforming analysis files.</li>
+					</ul>
+					<li>Enabled StaticCalendarDetector
+					</li>
+					<li>Reworked GUI2 to use standard FindBugs filters
+					</li>
+					<ul>
+					<li>Allow a suppression filter to be stored in a project and persisted to the XML representation of a project.
+					</li>
+					</ul>
+					
+					<li>Move away from old GUI2 save format (a directory containing an xml file and another file containing serialized filters).
+					</li>
+					<li>Support/recommend use of two new file extensions/formats:
+					<dl><dt>.fba - FindBugs Analysis File</dt>
+					<dd>Exactly the same as an existing bug collection file stored in XML format, but using a distinct file extension
+					to make it easier to figure out which xml files contain FindBugs results.</dd>
+					<dt>.fbp - FindBugs Project File</dt><dd>Contains just the information needed to run FindBugs and display the results (e.g., the files to be analyzed, the auxiliary class path and the location of source files)</dl></li>
+					</ul>
+					<p> Changes since version 1.1.3</p>
+					<ul>
+					<li>Added -xml:withAbridgedMessages option to generate xml containing shorter messages.
+					    The messages will be shorted by doing things like eliding package names, and leaving off
+					    the source line from the LongMessage.
+					    These messages are appropriate if being used in a context where 
+					    the non-message components of the bug annotations will be used to provide more information
+					    (e.g., clicking on the message for a MethodAnnotation will display the source for the method).
+					<ul><li>FindBugsDisplayFeatures.setAbridgedMessages(true) can be used to generate abridged messages
+					    when FindBugs is being accessed directly (not via generated XML) from a GUI or IDE.
+					    </li>
+					    </ul>
+					<li>In null pointer analysis, try to be better about always showing two locations: where it is known null and
+					where it is dereferenced.
+					<li>Interprocedural analysis of which methods return nonnull values
+					<li>Use method calls to select order in which classes are analyzed, and order in which methods
+					are analyzed, to improve interprocedural analysis results.
+					<li>Significant improvements in memory footprint, memory allocation and CPU utilization 
+					    (20-30% reduction in all three) 
+					<li>Added a project name, to provide better descriptions in the HTML output.
+					<li>Added new bug pattern: Casting to char, or bit masking with nonnegative value, and then checking to see
+						if the result is negative.
+					<li>Stopped reporting transient fields
+					of classes not marked as serializable. Transient is used by other persistence frameworks.
+					<li>Improvements to detector for SQL injection (Thanks to <a href="http://www.clock.org/~matt">Matt Hargett</a> for
+					his contributions
+					<li>Changed open/save options in GUI2 to not distinguish between FindBugs projects
+					and saved FindBugs analysis results.
+					<li>Improvements to detection of serious non-short-circuit evaluation.
+					<li>Updated Japanese localization (thanks to Ruimo Uno)
+					
+					<li>Eclipse plugin changes:
+					<ul>
+					<li>Created Bug User Annotations and Bug Tree Views
+					<li>Use different icons for different bug priorities
+					<li>Provide more information in Bug Details view
+					</ul>
+					</ul>
+					
+					<p>
+						Changes since version 1.1.2:
+					</p>
+					<ul>
+					<li>Fixed broken Ant task
+					<li>Added running ant task to smoke test
+					<li>Added validating xml and html output to smoke test
+					<li>Fixed some  (but not all) issues with html output validation
+					<li>Added check for x.equals(x) and x.compareTo(x)
+					<li>Various bug fixes
+					</ul>
+					<p>
+						Changes since version 1.1.1:
+					</p>
+					<ul>
+						<li>
+							Added check for infinite iterative loops
+						</li>
+						<li>
+							Added check for use of incompatible types in a collection (e.g.,
+							checking to see if a Set&lt;String&gt; contains a StringBuffer).
+						</li>
+						<li>
+							Added check for invocations of equals or hashCode on a URL,
+							which,
+							<a
+								href="http://michaelscharf.blogspot.com/2006/11/javaneturlequals-and-hashcode-make.html">surprising
+								many people</a>, requires DNS resolution.
+						</li>
+						<li>
+							Added check for classes that define compareTo but not equals;
+							such classes can exhibit some anomalous behavior (e.g., they are
+							treated differently by PriorityQueues in Java 5 and Java 6).
+						</li>
+						<li>
+							Added a check for useless self operations (e.g., x &lt; x or x ^ x).
+						</li>
+						<li>
+							Fixed a data race that could cause the GUI to fail on startup
+						</li>
+						<li>
+							Partial internationalization of the new GUI
+						</li>
+						<li>
+							Fix bug in "Redo analysis" option of new GUI
+						</li>
+						<li>
+							Tuning to reduce false positives
+						</li>
+						<li>
+							Fixed a bug in null pointer analysis that was generating false
+							positive null pointer warnings on exception paths. Fixing this
+							bug eliminates about 1/4 of the warnings on null pointer
+							exceptions on exception paths.
+						</li>
+						<li>
+							Fixed a bug in the processing of phi nodes for fields in the null
+							pointer analysis
+						</li>
+						<li>
+							Applied contributed patch that provides more quick fixes in
+							Eclipse plugin.
+						</li>
+						<li>
+						Fixed a number of bugs in the Eclipse auto update sites, and in the way
+						date qualifiers were being used in the Eclipse plugin. You may need to manually
+						disable your existing version of the plugin and download the 1.1.2 from the update 
+						site to get the automatic update function working correctly.
+						The Eclipse update sites are described at <a href="http://findbugs.cs.umd.edu/eclipse/">http://findbugs.cs.umd.edu/eclipse/</a>.
+						
+						</li>
+						<li>
+							Fixed progress bar in Eclipse plugin
+						</li>
+						<li>
+							A number of other bug fixes.
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 1.1.0:
+					</p>
+					<ul>
+						<li>
+							less scanning of classes not on the analysis path (This was
+							causing some performance problems.)
+						</li>
+						<li>
+							no unread field warnings for fields annotated with
+							javax.persistent or javax.ejb3
+						</li>
+						<li>
+							Eclipse plugin
+							<ul>
+								<li>
+									bug annotation info displayed in Bug Details tab
+								</li>
+								<li>
+									.fbwarnings data file now stored in .metadata (not in the
+									project itself)
+								</li>
+							</ul>
+						</li>
+						<li>
+							new SE_BAD_FIELD_INNER_CLASS pattern
+						</li>
+						<li>
+							updates to Japanese translation (ruimo)
+						</li>
+						<li>
+							fix some internal slashed/dotted path confusion
+						</li>
+						<li>
+							other minor improvements
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 1.0.0:
+					</p>
+
+					<ul>
+						<li>
+							Overall, the change from FindBugs 1.0.0 to FindBugs 1.1.0 has
+							been a big change. We've done a lot of work in a lot of areas,
+							and aren't even going to try to enumerate all the changes.
+						</li>
+						<li>
+							We spent a lot of time reviewing the results generated by
+							FindBugs for open source and commercial code bases, and made a
+							number of changes, small and large, to minimize the number of
+							false positives. Our primary focus for this was warnings reported
+							as high and medium priority correctness warnings. Our internal
+							evaluation is that we produce very few high/medium priority
+							correctness warnings where the analysis is actually wrong, and
+							that more than 75% of the high/medium priority correctness
+							warnings correspond to real coding defects that need addressing
+							in the source code. The remaining 25% are largely cases such as a
+							branch or statement that if taken would lead to an error, but in
+							fact is a dead branch or statement that can never be taken. Such
+							coding is confusing and hard to maintain, so it should arguably
+							be fixed, but it is unlikely to actually result in an error
+							during execution. Thus, some might classify those warnings as
+							false positives.
+
+						</li>
+						<li>
+							We've substantially improved the analysis for errors that could
+							result in null pointer dereferences. Overall, our experience has
+							been that these changes have roughly doubled the number of null
+							pointer errors we detect, without increasing the number of false
+							positives (in fact, our false positive rate has gone down). The
+							improvements are due to four factors:
+							<ul>
+								<li>
+									By default, we now do some interprocedural analysis to
+									determine methods that unconditionally dereference their
+									parameters.
+								</li>
+								<li>
+									FindBugs also comes with a model of which JDK methods
+									unconditionally dereference their parameters.
+								</li>
+								<li>
+									We do limited tracking of fields, so that we can detect null
+									values stored in fields that lead to exceptions.
+								</li>
+								<li>
+									We implemented a new analysis technique to find guaranteed
+									dereferences. Consider the following example:
+
+									<code>
+										<pre>public int f(Object x, boolean b) {
+  int result = 0;
+  if (x == null) result++;
+  else result--;
+  // at this point, we know x is null on a simple path
+  if (b) {
+    // at this point, x is only null on a complex path
+    // we don't know if the path in which x is null and b is true is feasible
+    return result + x.hashCode();
+    }
+  else {
+    // at this point, x is only null on a complex path
+    // we don't know if the path in which x is null and b is false is feasible
+    return result - x.hashCode();
+    }
+</pre>
+									</code>
+
+									<p>
+										FindBugs 1.0 used forward dataflow analysis to determine
+										whether each value is definitely null, null on a simple path,
+										possible null on a complex path, or definitely nonnull. Thus,
+										at the statement where
+										<code>
+											result
+										</code>
+										is decremented, we know that
+										<code>
+											x
+										</code>
+										is definitely null, and at the point before
+										<code>
+											if (b)
+										</code>
+										, we know that
+										<code>
+											x
+										</code>
+										is null on a simple path. If
+										<code>
+											x
+										</code>
+										were to be dereferenced here, we would generate a warning,
+										because if the else branch of the
+										<code>
+											if (x == null)
+										</code>
+										were ever taken, a null pointer exception would result.
+									</p>
+
+									<p>
+										However, in both the then and else branches of the
+										<code>
+											if (b)
+										</code>
+										statement,
+										<code>
+											x
+										</code>
+										is only null on a complex path that may be infeasible. It
+										might be that the program logic is such that if
+										<code>
+											x
+										</code>
+										is null, then
+										<code>
+											b
+										</code>
+										is never true, so generating a warning about the dereference
+										in the then clause might be a false positive. We could try to
+										analyze the program to determine whether it is possible for
+										<code>
+											x
+										</code>
+										to be null and
+										<code>
+											b
+										</code>
+										to be true, but that can be a hard analysis problem.
+									</p>
+
+									<p>
+										However,
+										<code>
+											x
+										</code>
+										is dereferenced in both the then
+										<em>and</em> else branches of the
+										<code>
+											if (b)
+										</code>
+										statement. So at the point immediately before
+										<code>
+											if (b)
+										</code>
+										, we know that
+										<code>
+											x
+										</code>
+										is null on a simple path
+										<em>and</em> that
+										<code>
+											x
+										</code>
+										is guaranteed to be dereferenced on all paths from this point
+										forward. FindBugs 1.1 performs a backwards data flow analysis
+										to determine the values that are guaranteed to be
+										dereferenced, and will generate a warning in this case.
+									</p>
+								</li>
+							</ul>
+							<p>
+								The following screen shot of our new GUI shows an example of
+								this analysis, as well as showing off our new GUI and points out
+								a limitation of our current plugins for Eclipse and NetBeans.
+								The screen shot shows a null pointer bug in HelpDisplay.java.
+								The test for
+								<code>
+									href!=null
+								</code>
+								on line 78 suggests that
+								<code>
+									href
+								</code>
+								could be null. If it is, then
+								<code>
+									href
+								</code>
+								will be dereferenced on either line 87 or on line 90, generating
+								a NPE. Note that our analysis here also understands that passing
+								<code>
+									href
+								</code>
+								to
+								<code>
+									URLEncoder.encode
+								</code>
+								will deference it, and thus treats line 87 as a dereference,
+								even though
+								<code>
+									href
+								</code>
+								is not actually dereferenced at that line. Within our new GUI,
+								all of these locations are highlighted and listed in the summary
+								panel. In the original GUI (and in HTML output) we list all of
+								the locations, but only the primary location is highlighted by
+								the original GUI. In the Eclipse and NetBeans plugins, only the
+								primary location is displayed; fixing this is on our todo list
+								(contributions welcome).
+							</p>
+							<p>
+								<img src="guaranteedDereference.png" alt="">
+
+
+							</p>
+
+						</li>
+						<li>
+							Preliminary support for detectors using the frameworks other than
+							BCEL, such as the
+							<a href="http://asm.objectweb.org/">ASM</a> bytecode framework.
+							You may experiment with writing ASM-based detectors, but beware
+							the API may still change (which could possibly also affect
+							BCEL-based detectors). In general, we've started trying to move
+							away from a deep dependence on BCEL, but that change is only
+							partially complete. Probably best to just avoid this until we
+							complete more work on this. This change is only visible to
+							FindBugs plugin developers, and shouldn't be visible to FindBugs
+							users.
+						</li>
+						<li>
+							<p>
+								Bug categories (CORRECTNESS, MT_CORRECTNESS, etc.) are no longer
+								hard-coded, but rather defined in xml files associated with
+								plugins, including the core plugin which defines the standard
+								categories. Third-party plugins can define their own categories.
+							</p>
+						</li>
+						<li>
+							<p>
+								Several bug patterns have been moved from CORRECTNESS and STYLE
+								into a new category, BAD_PRACTICE. The English localization of
+								STYLE has changed from "Style" to "Dodgy."
+							</p>
+							<p>
+								In general, we've worked very hard to limit CORRECTNESS bugs to
+								be real programming errors and sins of commission. We have
+								reclassified as BAD_PRACTICE a number of bad design practices
+								that result in overly fragile code, such as defining an equals
+								method that doesn't accept null or defining class with a equals
+								method that inherits hashCode from class Object.
+							</p>
+							<p>
+								In general, our guidelines for deciding whether a bug should be
+								classified as CORRECTNESS, BAD_PRACTICE or STYLE are:
+							</p>
+							<dl>
+								<dt>
+									CORRECTNESS
+								</dt>
+								<dd>
+									A problem that we can recognize with high confidence and is an
+									issue that we believe almost all developers would want to
+									examine and address. We recommend that software teams review
+									all high and medium priority warnings in their entire code
+									base.
+								</dd>
+								<dt>
+									BAD_PRACTICE
+								</dt>
+								<dd>
+									A problem that we can recognize with high confidence and
+									represents a clear violation of recommended and standard coding
+									practice. We believe each software team should decide which bad
+									practices identified by FindBugs it wants to prohibit in the
+									team's coding standard, and take action to remedy violations of
+									those coding standards.
+								</dd>
+								<dt>
+									STYLE
+								</dt>
+								<dd>
+									These are places where something strange or dodgy is going on,
+									such as a dead store to a local variable. Typically, less than
+									half of these represent actionable programming defects.
+									Reviewing these warnings in any code under active development
+									is probably a good idea, but reviewing all such warnings in
+									your entire code base might be appropriate only in some
+									situations. Individual or team programming styles can
+									substantially influence the effectiveness of each of these
+									warnings (e.g., you might have a coding practice or style in
+									your group that confuses one of the detectors into generating a
+									lot of STYLE warnings); you will likely want to selectively
+									suppress or report the STYLE warnings that are effective for
+									your group.
+								</dd>
+							</dl>
+						</li>
+						<li>
+							Released a preliminary version of a new GUI (known internally as
+							GUI2 -- not very creative, huh?)
+						</li>
+						<li>
+							Provided standard ways to mark user designations of bug warnings
+							(e.g., as NOT_A_BUG or SHOULD_FIX). The internal logic now
+							records this, it is represented in the XML file, and GUI2 allows
+							the designations to be applied (along with free-form user
+							annotations about each warning). The user designations and
+							annotations are not yet supported by the Eclipse plugin, but we
+							clearly want to support it in Eclipse shortly.
+						</li>
+						<li>
+							Added a check for a bad comparison with a signed byte with a
+							value not in the range -128..127. For example:
+							<code>
+								<pre>boolean find200(byte b[]) {
+  for(int i = 0; i &lt; b.length; i++) if (b[i] == 200) return i;
+  return -1;
+}
+</pre>
+							</code>
+						</li>
+						<li>
+							Added a checking for testing if a value is equal to Double.NaN
+							(no value is equal to NaN, not even NaN).
+						</li>
+						<li>
+							Added a check for using a class with an equals method but no
+							hashCode method in a hashed data structure.
+						</li>
+						<li>
+							Added check for uncallable method of an anonymous inner class.
+							For example, in the following code, it is impossible to invoke
+							the initalValue method (because the name is misspelled and as a
+							result is doesn't override a method in ThreadLocal).
+							<code>
+								<pre>private static ThreadLocal serialNum = new ThreadLocal() {
+         protected synchronized Object initalValue() {
+             return new Integer(nextSerialNum++);
+         }
+     };
+</pre>
+							</code>
+						</li>
+						<li>
+							Added check for a dead local store caused by a switch statement
+							fall through
+						</li>
+						<li>
+							Added check for computing the absolute value of a random 32 bit
+							integer or of a hashcode. This is broken because
+							<code>
+								Math.abs(Integer.MIN_VALUE) == Integer.MIN_VALUE
+							</code>
+							, and thus result of calling Math.abs, which is expected to be
+							nonnegative, will in fact be negative one time out of 2
+							<sup>
+								32
+							</sup>
+							, which will invariably be the time your boss is demoing the
+							software to your customers.
+
+						</li>
+						<li>
+							More careful resolution of inherited methods and fields. Some of
+							the shortcuts we were taking in FindBugs 1.0.0 were leading to
+							inaccurate results, and it was fairly easy to address this by
+							making the analysis more accurate.
+						</li>
+						<li>
+							Overall, analysis times are about 1.6 times longer in FindBugs
+							1.1.0 than in FindBugs 1.0.0. This is because we have enabled
+							substantial additional analysis at the default effort level (the
+							actual analysis engine is significantly faster than in FindBugs
+							1.0). On a recent AMD Athlon processor, analyzing JDK1.6.0 (about
+							1 million lines of code) requires about 15 minutes of wall clock
+							time.
+						</li>
+						<li>
+							Provided class and script (printClass) to print classfile in the
+							human readable format produced by BCEL
+						</li>
+						<li>
+							Provided -findSource option to setBugDatabaseInfo
+						</li>
+					</ul>
+
+
+					<p>
+						Changes since version 0.9.7:
+					</p>
+
+					<ul>
+						<li>
+							fix ObjectTypeFactory bug that was suppressing some bugs
+						</li>
+						<li>
+							opcode stack may determine definite zeros on some paths
+						</li>
+						<li>
+							opcode stack can track some constant string concatenations
+							(dbrosius)
+						</li>
+						<li>
+							default effort performs iterative opcode analysis (but min effort
+							does not)
+						</li>
+						<li>
+							default heap size upped to 384m
+						</li>
+						<li>
+							schema for XML output available: bugcollection.xsd
+						</li>
+						<li>
+							fixed some internal confusion between dotted and slashed class
+							names
+						</li>
+						<li>
+							New detectors
+							<ul>
+								<li>
+									CheckImmutableAnnotation.java: checks JCIP annotations
+								</li>
+							</ul>
+						</li>
+						<li>
+							Updated detectors
+							<ul>
+								<li>
+									BadRegEx.java: understands Pattern.LITERAL, warns about "."
+								</li>
+								<li>
+									FindUnreleasedLock.java: fewer false positives
+								</li>
+								<li>
+									DumbMethods.java: check for vacuous comparisons to MAX_INTEGER
+									or MIN_INTEGER, fix bugs detecting DM_NEXTINT_VIA_NEXTDOUBLE
+								</li>
+								<li>
+									FindPuzzlers.java: detect
+									<tt>n%2==1</tt>, detect toString() on array types
+								</li>
+								<li>
+									FindInconsistentSync2.java: detects IS_FIELD_NOT_GUARDED
+								</li>
+								<li>
+									MethodReturnCheck.java: add check for discarded newly
+									constructed values, increase priority of some ignored
+									constructed exceptions, better handling of bytecode compiled by
+									Eclipse
+								</li>
+								<li>
+									FindEmptySynchronizedBlock.java: better handling of bytecode
+									compiled by Eclipse
+								</li>
+								<li>
+									DoInsideDoPrivileged.java: warn if call to setAccessible isn't
+									in doPriviledged, don't report private methods
+								</li>
+								<li>
+									LoadOfKnownNullValue.java: fix bug that was reporting false
+									positives on
+									<code>
+										finally
+									</code>
+									blocks
+								</li>
+								<li>
+									CheckReturnAnnotationDatabase.java: better checks for unstarted
+									threads
+								</li>
+								<li>
+									ConfusionBetweenInheritedAndOuterMethod.java: fewer false
+									positives, fixed a package-handling bug
+								</li>
+								<li>
+									BadResultSetAccess.java: separate bug pattern for
+									PreparedStatements,
+									<code>
+										BRZA
+									</code>
+									category folded into
+									<code>
+										SQL
+									</code>
+									category
+								</li>
+								<li>
+									FindDeadLocalStores.java, FindBadCast2.java, DumbMethods.java,
+									RuntimeExceptionCapture.java: coalesce similar bugs within a
+									method into a single bug instance with multiple source lines
+								</li>
+							</ul>
+						</li>
+						<li>
+							Eclipse plugin
+							<ul>
+								<li>
+									plugin ID changed from
+									<tt>de.tobject.findbugs</tt> to
+									<tt>edu.umd.cs.findbugs.plugin.eclipse</tt>
+								</li>
+								<li>
+									support for findbugs eclipse auto-update site
+								</li>
+							</ul>
+						</li>
+						<li>
+							Updated test case files
+							<ul>
+								<li>
+									BadRegEx.java
+								</li>
+								<li>
+									JSR166.java
+								</li>
+								<li>
+									ConcurrentModificationBug.java
+								</li>
+								<li>
+									DeadStore.java
+								</li>
+								<li>
+									InstanceOf.java
+								</li>
+								<li>
+									LoadKnownNull.java
+								</li>
+								<li>
+									NeedsToCheckReturnValue.java
+								</li>
+								<li>
+									BadResultSetAccessTest.java
+								</li>
+								<li>
+									DeadStore.java
+								</li>
+								<li>
+									TestNonNull2.java
+								</li>
+								<li>
+									TestImmutable.java
+								</li>
+								<li>
+									TestGuardedBy.java
+								</li>
+								<li>
+									BadRandomInt.java
+								</li>
+								<li>
+									six test cases added to new
+									<code>
+										TigerTraps
+									</code>
+									directory
+								</li>
+							</ul>
+						</li>
+						<li>
+							fix bug that was generating duplicate uids
+						</li>
+						<li>
+							fix bug with
+							<code>
+								-onlyAnalyze some.package.*
+							</code>
+							on jdk1.4
+						</li>
+						<li>
+							fix regression bug in DismantleByteCode.getRefConstantOperand()
+						</li>
+						<li>
+							fix some minor bugs with the Swing GUI
+						</li>
+						<li>
+							reordered some bugInstances so that source line annotations come
+							last
+						</li>
+						<li>
+							removed references to unused java system properties
+						</li>
+						<li>
+							French translation updates (David Cotton)
+						</li>
+						<li>
+							Japanese translation updates (Hanai Shisei)
+						</li>
+						<li>
+							content cleanup for findbugs.xml and messages.xml
+						</li>
+						<li>
+							references to cvs hostname updated to
+							findbugs.cvs.sourceforge.net
+						</li>
+						<li>
+							documented xdoc output options, new
+							mineBugHistory/computeBugHistory options
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.9.6:
+					</p>
+
+					<ul>
+						<li>
+							performance improvements
+						</li>
+						<li>
+							ObjectType instances are cached to reduce memory footprint
+						</li>
+						<li>
+							for performance and memory reasons stateless detectors are no
+							longer cloned, must clear their own state between .class files
+						</li>
+						<li>
+							fixed bug in bytecode-set lookup for methods (was causing bad
+							results for IS2, perhaps others)
+						</li>
+						<li>
+							fix some OpcodeStack bugs with integer and long operations,
+							perform iterative analysis when effort is
+							<tt>max</tt>
+						</li>
+						<li>
+							HTML output includes LongMessage text again (regression in 0.95 -
+							0.96)
+						</li>
+						<li>
+							New detectors
+							<ul>
+								<li>
+									CalledMethods.java: builds a list of invoked methods for other
+									detectors to consult (non-reporting)
+								</li>
+								<li>
+									UncallableMethodOfAnonymousClass.java: detect anonymous inner
+									classes that define methods that are probably intended to but
+									do not override methods in a superclass.
+								</li>
+							</ul>
+						</li>
+						<li>
+							Updated detectors
+							<ul>
+								<li>
+									FindFieldSelfAssignment.java: recognize separate fields with
+									the same name (one from superclass)
+								</li>
+								<li>
+									FindLocalSelfAssignment2.java: handles backward branches better
+									(Dave Brosius)
+								</li>
+								<li>
+									FindBadCast2.java: BC_NULL_INSTANCEOF changed to
+									NP_NULL_INSTANCEOF
+								</li>
+								<li>
+									FindPuzzlers.java: eliminate false positive on setDate() (Dave
+									Brosius)
+								</li>
+							</ul>
+						</li>
+						<li>
+							Eclipse plugin
+							<ul>
+								<li>
+									fix serious threading bug
+								</li>
+								<li>
+									preferences for Filters and effort (Peter Hendriks)
+								</li>
+								<li>
+									French localization (David Cotton)
+								</li>
+								<li>
+									fix bug when reporting inner classes (Peter Friese)
+								</li>
+							</ul>
+						</li>
+						<li>
+							Updated test case files
+							<ul>
+								<li>
+									Mwn.java (Carl Burke/Dave Brosius)
+								</li>
+								<li>
+									DumbMethodInvocations.java (Anto paul/Dave Brosius)
+								</li>
+								<!--sic-->
+							</ul>
+						</li>
+						<li>
+							XML output includes garbage collection duration
+						</li>
+						<li>
+							French messages updated (David Cotton)
+						</li>
+						<li>
+							Swing GUI shows file name after Load Bugs command
+						</li>
+						<li>
+							Ant task to launch the findbugs frame (Mark McKay)
+						</li>
+						<li>
+							miscellaneous code cleanup
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.9.5:
+					</p>
+
+					<ul>
+						<li>
+							Updated detectors
+							<ul>
+								<li>
+									FindNullDeref.java: respect NonNull and CheckForNull field
+									annotations
+								</li>
+								<li>
+									SerializableIdiom.java: detect non-private readObject and
+									writeObject methods
+								</li>
+								<li>
+									FindRefComparison.java: smarter array comparison detection
+								</li>
+								<li>
+									IsNullValueAnalysis.java: detect
+									<tt>null instanceof</tt>
+								</li>
+								<li>
+									FindLocalSelfAssignment2.java: suppress some false positives
+									(Dave Brosius)
+								</li>
+								<li>
+									FindUnreleasedLock.java: don't waste time processing classes
+									that don't refer to java.util.concurrent.locks
+								</li>
+								<li>
+									MutableStaticFields.java: report the source line (Dave Brosius)
+								</li>
+								<li>
+									SwitchFallthrough.java: better handling of System.exit() (Dave
+									Brosius)
+								</li>
+								<li>
+									MultithreadedInstanceAccess.java: better handling of
+									Servlet.init() (Dave Brosius)
+								</li>
+								<li>
+									ConfusionBetweenInheritedAndOuterMethod.java: now enabled
+								</li>
+							</ul>
+						</li>
+						<li>
+							Eclipse plugin
+							<ul>
+								<li>
+									background processing (Peter Friese)
+								</li>
+								<li>
+									internationalization, Japanese localization (Takashi Okamoto)
+								</li>
+							</ul>
+						</li>
+						<li>
+							findbugs
+							<tt>-onlyAnalyze</tt> option now works on windows platforms
+						</li>
+						<li>
+							mineBugHistory
+							<tt>-noTabs</tt> option for better alignment of output columns
+						</li>
+						<li>
+							filterBugs
+							<tt>-fixed</tt> option (also: will now recognize the most recent
+							version string)
+						</li>
+						<li>
+							XML output includes running time and memory usage data
+						</li>
+						<li>
+							miscellaneous minor corrections to the manual
+						</li>
+						<li>
+							better bytecode analysis of the
+							<tt>iinc</tt> instruction
+						</li>
+						<li>
+							fix bug in null pointer analysis
+						</li>
+						<li>
+							improved catch block heuristics
+						</li>
+						<li>
+							some type analysis tweaks
+						</li>
+						<li>
+							Bug priority changes
+							<ul>
+								<li>
+									DumbMethodInvocations.java: decrease priority of hard-coded
+									<tt>/tmp</tt> filenames
+								</li>
+								<li>
+									ComparatorIdiom.java: decrease priority of non-serializable
+									anonymous comparators
+								</li>
+								<li>
+									FindSqlInjection.java: decrease priority of appending a
+									constant or a static
+								</li>
+							</ul>
+						</li>
+						<li>
+							Updated bug explanations
+							<ul>
+								<li>
+									NM_VERY_CONFUSING (Dave Brosius)
+								</li>
+							</ul>
+						</li>
+						<li>
+							Updated test case files
+							<ul>
+								<li>
+									BadStoreOfNonSerializableObject.java
+								</li>
+								<li>
+									BadRandomInt.java
+								</li>
+								<li>
+									TestFieldAnnotations.java
+								</li>
+								<li>
+									UseInitCause.java
+								</li>
+								<li>
+									SqlInjection.java
+								</li>
+								<li>
+									ArrayEquality.java
+								</li>
+								<li>
+									BadIntegerOperations.java
+								</li>
+								<li>
+									Pilhuhn.java
+								</li>
+								<li>
+									InstanceOf.java
+								</li>
+								<li>
+									SwitchFallthrough.java (Dave Brosius)
+								</li>
+							</ul>
+						</li>
+						<li>
+							fix URL decoding bug when running under Java Web Start (Dave
+							Brosius)
+						</li>
+						<li>
+							distribution includes
+							<tt>project.xml</tt> file for NetBeans
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.9.4:
+					</p>
+					<ul>
+						<li>
+							New detectors
+							<ul>
+								<li>
+									VarArgsProblems.java
+								</li>
+								<li>
+									FindSqlInjection.java: now enabled
+								</li>
+								<li>
+									ComparatorIdiom.java: comparators usually implement
+									serializable
+								</li>
+								<li>
+									Naming.java: detect methods not overridden due to eponymously
+									typed args from different packages
+								</li>
+							</ul>
+						</li>
+						<li>
+							Updated detectors
+							<ul>
+								<li>
+									SwitchFallthrough.java: surpress some false positives
+								</li>
+								<li>
+									DuplicateBranches.java: surpress some false positives
+								</li>
+								<li>
+									IteratorIdioms.java: surpress some false positives
+								</li>
+								<li>
+									FindHEmismatch.java: surpress some false positives
+								</li>
+								<li>
+									QuestionableBooleanAssignment.java: finds more cases of
+									<tt>if (b=true)</tt> ilk
+								</li>
+								<li>
+									DumbMethods.java: detect int remainder by 1, delayed gc errors
+								</li>
+								<li>
+									SerializableIdiom.java: detect store of nonserializable object
+									into field of serializable class
+								</li>
+								<li>
+									FindNullDeref.java: fix potential exception
+								</li>
+								<li>
+									IsNullValue.java: fix potential exception
+								</li>
+								<li>
+									MultithreadedInstanceAccess.java: fix potential exception
+								</li>
+								<li>
+									PreferZeroLengthArrays.java: flag the method, not the line
+								</li>
+							</ul>
+						</li>
+						<li>
+							Remove some inadvertent dependencies on JDK 1.5
+						</li>
+						<li>
+							Sort order should be more consistent
+						</li>
+						<li>
+							XML output changes
+							<ul>
+								<li>
+									Option to sort XML bug output
+								</li>
+								<li>
+									Now contains instance IDs
+								</li>
+								<li>
+									uid no longer missing (was causing problems with fancy HTML
+									output)
+								</li>
+								<li>
+									Typo fixed
+								</li>
+							</ul>
+						</li>
+						<li>
+							Internal changes to track source files,
+							<tt>-sourceInfo</tt> option
+						</li>
+						<li>
+							Bug matching: first try exact bug pattern matching, option to
+							compare priorities, option to disable package moves
+						</li>
+						<li>
+							Architecture documentation in
+							<tt>design/architecture</tt>
+						</li>
+						<li>
+							Test cases move into their own CVS project
+						</li>
+						<li>
+							Don't report warnings that occur outside the analyzed classes
+						</li>
+						<li>
+							Fixes to the build.xml files
+						</li>
+						<li>
+							Better handling of @CheckReturnValue and @CheckForNull
+							annotations (also, some additional methods searched for check
+							return value and check for null)
+						</li>
+						<li>
+							Fixed some stream-closing bugs (one by
+							<tt>z-fb-user</tt>/Dave Brosius)
+						</li>
+						<li>
+							Bug priority changes
+							<ul>
+								<li>
+									increase priority of ignoring return value of
+									java.sql.Connection methods
+								</li>
+								<li>
+									increase priority of comparing classes like Integer using
+									<tt>==</tt>
+								</li>
+								<li>
+									decrease priority of IT_NO_SUCH_ELEMENT if we see any call to
+									<tt>next()</tt>
+								</li>
+								<li>
+									tweak priority of NM_METHOD_CONSTRUCTOR_CONFUSION
+								</li>
+								<li>
+									decrease priority of RV_RETURN_VALUE_IGNORED for an inherited
+									annotation that doesn't return same type as class
+								</li>
+							</ul>
+						</li>
+						<li>
+							Updated bug explanations
+							<ul>
+								<li>
+									RCN_REDUNDANT_NULLCHECK_WOULD_HAVE_BEEN_A_NPE
+								</li>
+								<li>
+									DP_CREATE_CLASSLOADER_INSIDE_DO_PRIVILEGED
+								</li>
+								<li>
+									IMA_INEFFICIENT_MEMBER_ACCESS (Dave Brosius)
+								</li>
+								<li>
+									some Japanese improvements to messages_ja.xml (
+									<tt>ruimo</tt>)
+								</li>
+								<li>
+									some German improvements to findbugs_de.properties (Dave
+									Brosius,
+									<tt>dvholten</tt>)
+								</li>
+							</ul>
+						</li>
+						<li>
+							Updated test case files
+							<ul>
+								<li>
+									BadIntegerOperations.java
+								</li>
+								<li>
+									SecondKaboom.java
+								</li>
+								<li>
+									OpenDatabase.java (Dave Brosius)
+								</li>
+								<li>
+									FindOpenStream.java (Dave Brosius)
+								</li>
+								<li>
+									BadRandomInt.java
+								</li>
+							</ul>
+						</li>
+						<li>
+							Source-lines info maintained for methods (handy for abstract and
+							native methods)
+						</li>
+						<li>
+							Remove surrounding opcodes from source line annotations
+						</li>
+						<li>
+							Better error when can't read file
+						</li>
+						<li>
+							Swing GUI: removed console pane from FindBugsFrame, fix missing
+							classes bug
+						</li>
+						<li>
+							Fixes to OpcodeStack.java
+						</li>
+						<li>
+							Detectors may attach a custom value to an OpcodeStack.Item (Dave
+							Brosius)
+						</li>
+						<li>
+							Filter.java: ability to add text messages to XML output, fix bug
+							with
+							<tt>-withMessages</tt>
+						</li>
+						<li>
+							SourceInfoMap supports ranges of source lines
+						</li>
+						<li>
+							Ant task supports the
+							<tt>timestampNow</tt> attribute
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.9.3:
+					</p>
+					<ul>
+						<li>
+							Substantial rework of datamining code
+						</li>
+						<li>
+							Removed bogus warnings about await on things other than Condition
+							not being in a loop
+						</li>
+						<li>
+							Fixed bug in OpcodeStack handling of dup2 of long/double values
+						</li>
+						<li>
+							Don't report array types as missing classes
+						</li>
+						<li>
+							Adjustment of some warnings on ignored return values
+						</li>
+						<li>
+							Added thread safety annotations from Java Concurrency in Practice
+							(no detectors written for these yet)
+						</li>
+						<li>
+							Added annotation for methods that, if overridden, should be
+							invoked by overriding methods via a call to super
+						</li>
+						<li>
+							Updated -html:fancy.xsl (Etienne Giraudy)
+						</li>
+					</ul>
+
+					<p>
+						Note: there was no version 0.9.2
+					</p>
+
+					<p>
+						Changes since version 0.9.1:
+					</p>
+					<ul>
+						<!-- New detectors -->
+						<li>
+							Embellish USM to find abstract methods that implement an
+							interface method (Dave Brosius)
+						</li>
+						<li>
+							New detector to find stores of literal booleans inside if or
+							while expressions (Dave Brosius)
+						</li>
+						<li>
+							New style detector to find final classes that declare protected
+							fields (Dave Brosius)
+						</li>
+						<li>
+							New detector to find subclass methods that simply forward,
+							verbatim, to the super class (Dave Brosius)
+						</li>
+						<li>
+							Detector to find instances where code is attempting to write an
+							object out via an implementation of DataOutput, but the object is
+							not guaranteed to be Serializable (Jon Christiansen, Bill Pugh)
+						</li>
+
+						<!-- Feature enhancements -->
+						<li>
+							Large (35%) analysis speedup (Bill Pugh)
+						</li>
+						<li>
+							Add line numbers to Swing GUI code panel (Dave Brosius)
+						</li>
+						<li>
+							Added effort options to Swing GUI (Dave Brosius)
+						</li>
+						<li>
+							Add ability to specify bugs file to open from command line for
+							GUI version, through -loadbugs (Phillip Martin)
+						</li>
+						<li>
+							New stylesheet for generating HTML: use option
+							<tt>-html:plain.xsl</tt> (Chris Nappin)
+						</li>
+						<li>
+							New stylesheet for generating HTML: use option
+							<tt>-html:fancy.xsl</tt> (Etienne Giraudy)
+						</li>
+						<li>
+							Updated Japanese bug message translations (Shisei Hanai)
+						</li>
+
+						<!-- Bug fixes -->
+						<li>
+							XHTML compliance fixes for bug details (Etienne Giraudy)
+						</li>
+						<li>
+							Various detector fixes (Shisei Hanai)
+						</li>
+						<li>
+							Fixed bugs in the project preferences dialog int the Eclipse
+							plugin (Takashi Okamoto, Thomas Einwaller)
+						</li>
+						<li>
+							Lowered priority of analysis thread in Swing GUI (David
+							Hovemeyer, suggested by Shisei Hanai and Jeffrey W. Badorek)
+						</li>
+						<li>
+							Fixed EclipsePlugin to correctly pick up auxclasspath entries
+							(Jon Christiansen)
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.9.0:
+					</p>
+					<ul>
+						<li>
+							Fixed dependence on JRE 1.5: all features should work on JRE 1.4
+							again
+						</li>
+						<li>
+							Fixed -effort command line option handling for Swing GUI
+						</li>
+						<li>
+							Fixed conserveSpace and workHard attributes int Ant task
+						</li>
+						<li>
+							Added support for effort attribute in Ant task
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.8.8:
+					</p>
+					<ul>
+						<!-- New detectors and bug patterns -->
+						<li>
+							XMLFactoryBypass detector to find direct allocation of xml class
+							implementations (Dave Brosius)
+						</li>
+						<li>
+							InefficientMemberAccess detector to find accesses to owning class
+							private members (Dave Brosius)
+						</li>
+						<li>
+							DuplicateBranches detector checks switch statements too (Dave
+							Brosius)
+						</li>
+
+						<!-- Feature enhancements -->
+						<li>
+							FindBugs available from findbugs.sourceforge.net as Java Web
+							Start application (Dave Brosius)
+						</li>
+						<li>
+							Updated Japanese bug message translations (Shisei Hanai)
+						</li>
+						<li>
+							Improved bug detail message for covariant equals() (Shisei Hanai)
+						</li>
+						<li>
+							Modeling of instanceof checks is now enabled by default, making
+							the bad cast detector much more useful (Bill Pugh, David
+							Hovemeyer)
+						</li>
+						<li>
+							Support for detector ordering constraints in plugin descriptor
+							(David Hovemeyer)
+						</li>
+						<li>
+							Simpler option to control analysis effort: -effort:
+							<i>value</i>, where
+							<i>value</i> is one of
+							<code>
+								min
+							</code>
+							,
+							<code>
+								default
+							</code>
+							, or
+							<code>
+								max
+							</code>
+							(David Hovemeyer)
+						</li>
+						<li>
+							Using -effort:max, FindNullDeref checks for null arguments passed
+							to methods which dereference them unconditionally (David
+							Hovemeyer)
+						</li>
+						<li>
+							FindNullDeref checks @Null and @NonNull annotations for
+							parameters and return values (David Hovemeyer)
+						</li>
+
+						<!-- Bug fixes -->
+					</ul>
+
+					<p>
+						Changes since version 0.8.7:
+					</p>
+
+					<ul>
+						<!-- New detectors and bug patterns -->
+						<li>
+							New detector to find duplicate code in if/else statements (Dave
+							Brosius)
+						</li>
+						<li>
+							Look for calls to wait() on Condition objects (David Hovemeyer)
+						</li>
+						<li>
+							Look for java.util.concurrent.Lock objects not released on every
+							path out of method (David Hovemeyer)
+						</li>
+						<li>
+							Look for calls to Thread.sleep() with a lock held (David
+							Hovemeyer)
+						</li>
+						<li>
+							More accurate detection of impossible casts (Bill Pugh, David
+							Hovemeyer)
+						</li>
+
+						<!-- Feature enhancements -->
+						<li>
+							Saved XML now contains project statistics (Jay Dunning)
+						</li>
+						<li>
+							Filter files can select by bug pattern type and warning priority
+							(David Hovemeyer)
+						</li>
+
+						<!-- Bug fixes -->
+						<li>
+							Restored some files inadvertently omitted from previous release
+							(Rohan Lloyd, David Hovemeyer)
+						</li>
+						<li>
+							Make sure detectors requiring JDK 1.5 runtime classes are only
+							executed if those classes are available (David Hovemeyer)
+						</li>
+						<li>
+							Don't display analysis error dialog unless there is really an
+							error (David Hovemeyer)
+						</li>
+						<li>
+							Updated and expanded French translations of bug patterns and
+							Swing GUI (Olivier Parent)
+						</li>
+						<li>
+							Fixed invalid character encoding in German Swing GUI translation
+							(Olivier Parent)
+						</li>
+						<li>
+							Fix locale used for date format in project stats (K. Hashimoto)
+						</li>
+						<li>
+							Fixed LongDescription elements in xml:withMessages output format
+							(K. Hashimoto)
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.8.6:
+					</p>
+
+					<ul>
+						<!-- new detectors -->
+						<li>
+							Extend Naming detector to look for classes that are named
+							XXXException but that are not Exceptions (Dave Brosius)
+						</li>
+						<li>
+							New detector to find classes that expose semaphores in the public
+							implementation through the 'this' reference. (Dave Brosius)
+						</li>
+						<li>
+							New Style detector to find Struts Action/Servlet derived classes
+							that reference instance member variable not in synchronized
+							blocks. (Dave Brosius)
+						</li>
+						<li>
+							New Style detector to find classes that declare implementation of
+							interfaces that are already implemented by super classes (Dave
+							Brosius)
+						</li>
+						<li>
+							New Style detector to find circular dependencies between classes
+							(Dave Brosius)
+						</li>
+						<li>
+							New Style detector to find unnecessary math on constants (Dave
+							Brosius)
+						</li>
+						<li>
+							New detector to find equality comparisons using floating point
+							math (Jay Dunning)
+						</li>
+						<li>
+							New faster detector to find local self assignments (Bill Pugh)
+						</li>
+						<li>
+							New detector to find infinite recursive loops (Bill Pugh)
+						</li>
+						<li>
+							New detector to find for loops with an incorrect increment (Bill
+							Pugh)
+						</li>
+						<li>
+							New detector to find suspicious uses of BufferedReader.readLine()
+							and String.indexOf() (Bill Pugh)
+						</li>
+						<li>
+							New detector to find suspicious integer to double casts (David
+							Hovemeyer, Bill Pugh)
+						</li>
+						<li>
+							New detector to find invalid regular expression patterns (Bill
+							Pugh)
+						</li>
+						<li>
+							New detector to find Bloch/Gafter Java puzzlers (Bill Pugh)
+						</li>
+
+						<!-- feature enhancements -->
+						<li>
+							New system property to suppress reporting of DLS based on local
+							variable name (Glenn Boysko)
+						</li>
+						<li>
+							Enhancements to configuration dialog in Eclipse plugin, allow for
+							saving enabled detectors in Eclipse projects (Phil Crosby)
+						</li>
+						<li>
+							Sortable columns in detector dialog (Dave Brosius)
+						</li>
+						<li>
+							New tab in gui for showing bugs grouped by category (Dave
+							Brosius)
+						</li>
+						<li>
+							Improved German translation of Swing GUI (Thomas Kuehne)
+						</li>
+						<li>
+							Improved source file reporting in Emacs output format (Len Trigg)
+						</li>
+						<li>
+							Improvements to redundant null comparison detector (Bill Pugh)
+						</li>
+						<li>
+							Localization of run analysis and analysis error dialogs in Swing
+							GUI (K. Hashimoto)
+						</li>
+
+						<!-- Bug fixes -->
+						<li>
+							Don't scan equals methods in FindHEMismatch if code is native
+							(Greg Bentz)
+						</li>
+						<li>
+							French translation fixes (David Cotton)
+						</li>
+						<li>
+							Internationalization report fixes (K. Hashimoto)
+						</li>
+						<li>
+							Japanese translations updates (SHISEI Hanai)
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.8.5:
+
+					</p>
+					<ul>
+						<!-- new detectors -->
+						<li>
+							New detector to find catch blocks that may inadvertently catch
+							runtime exceptions (Brian Goetz)
+						</li>
+						<li>
+							New detector to find objects that are instantiated based on
+							classes that only have static methods and fields, using the
+							synthesized constructor (Dave Brosius)
+						</li>
+						<li>
+							New detector to find calls to Thread.interrupted() in a non
+							static context, and especially with non currentThread() threads
+							(Dave Brosius)
+						</li>
+						<li>
+							New detector to find calls to equals() methods that use Object's
+							version. (Dave Brosius)
+						</li>
+						<li>
+							New detector to find Applets that call methods in the constructor
+							refering to the AppletStub (Dave Brosius)
+						</li>
+						<li>
+							New detector to find some cases of infinite recursion (Bill Pugh)
+						</li>
+						<li>
+							New detector to find dead stores to local variables (David
+							Hovemeyer, Bill Pugh)
+						</li>
+						<li>
+							Extend Dumb Method detector for toUpperCase(), toLowerCase()
+							without a locale, new Integer(1).toString(), new
+							XXX().getClass(), and new Thread() without a run implementation
+							(Dave Brosius)
+							<!-- feature enhancements -->
+						</li>
+						<li>
+							Ant task supports "errorProperty" attribute, which sets an Ant
+							property to "true" if an error occurs running FindBugs (Michael
+							Tamm)
+						</li>
+						<li>
+							Eclipse plugin allows filtering of warnings by bug category,
+							priority (David Hovemeyer)
+						</li>
+						<li>
+							Swing GUI allows filtering of warnings by bug category (David
+							Hovemeyer)
+						</li>
+						<li>
+							Ability to annotate methods using Java 1.5 annotations that
+							suppress FindBugs warnings (Bill Pugh)
+						</li>
+						<li>
+							New -adjustExperimental for lowering priority of BugPatterns that
+							are experimental (Dave Brosius)
+						</li>
+						<li>
+							Allow for command line options 'files' using the @ symbol (David
+							Hovemeyer)
+						</li>
+						<li>
+							New -adjustPriority command line option to for adjusting bug
+							priorites (David Hovemeyer)
+						</li>
+						<li>
+							Added an Edit menu (cut/copy/paste) to Swing GUI (Dave Brosius)
+						</li>
+						<li>
+							French translation supplied (David Cotton)
+							<!-- Bug fixes -->
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.8.4:
+
+					</p>
+					<ul>
+						<!-- new detectors -->
+						<li>
+							New detector for volatile references to arrays (Bill Pugh)
+						</li>
+						<li>
+							New detector to find instanceof usage where inheritance can be
+							determined statically (Dave Brosius)
+						</li>
+						<li>
+							New detector to find ResultSet.getXXX updateXXX calls using index
+							0 (Dave Brosius)
+						</li>
+						<li>
+							New detector to find empty zip or jar entries (Bill Pugh)
+
+							<!-- feature enhancements -->
+						</li>
+						<li>
+							HTML output generation using built-in XSLT stylesheet or
+							user-defined stylesheet (David Hovemeyer)
+						</li>
+						<li>
+							Allow URLs to be specified to analyze zip/jar files, local
+							directories, and single classfiles (David Hovemeyer)
+						</li>
+						<li>
+							New command line option -onlyAnalyze restricts analysis to
+							selected classes and packages without reducing accuracy (David
+							Hovemeyer)
+						</li>
+						<li>
+							Allow Swing GUI to show source code in jar files on Windows
+							systems (Dave Brosius)
+
+							<!-- Bug fixes -->
+						</li>
+						<li>
+							Fix the Switch Fall Thru detector (Dave Brosius, David Hovemeyer,
+							Bill Pugh)
+						</li>
+						<li>
+							MacOS GUI fixes (Rohan Lloyd)
+						</li>
+						<li>
+							Fix false positive in BOA in case where method is correctly and
+							'incorrectly' overridden (Dave Brosius)
+						</li>
+						<li>
+							Fixed memory blowup when analyzing methods which access a large
+							number of fields (David Hovemeyer)
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.8.3:
+					</p>
+					<ul>
+						<li>
+							Initial and preliminary localization of the Swing GUI.&nbsp;
+							Translations by:
+							<ul>
+								<li>
+									German - Peter D. Stout, Holger Stenzhorn
+								</li>
+								<li>
+									Finnish - Juha Knuutila
+								</li>
+								<li>
+									Estonian - Tanel Lebedev
+								</li>
+								<li>
+									Japanese - Hanai Shisei
+								</li>
+							</ul>
+						</li>
+						<li>
+							Eliminated debug print statements inadvertently left enabled
+						</li>
+						<li>
+							Reverted some changes in the open stream detector: this should
+							fix some false positives that were introduced in the previous
+							release
+						</li>
+						<li>
+							Fixed a couple missing class reports
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.8.2:
+					</p>
+					<ul>
+
+						<!-- New detectors -->
+						<li>
+							New detector to find improperly overridden GUI Adapter classes
+							(Dave Brosius)
+						</li>
+						<li>
+							New detector to find improperly setup JUnit TestCases (Dave
+							Brosius)
+						</li>
+						<li>
+							New detector to find variables that mask class level fields (Dave
+							Brosius)
+						</li>
+						<li>
+							New detector to find comparisons of values computed with bitwise
+							operators that always yield the same result (Tom Truscott)
+						</li>
+						<li>
+							New detector to find unsafe getClass().getResource() calls (Bill
+							Pugh)
+						</li>
+						<li>
+							New detector to find GUI changes not in GUI thread but in static
+							main (Bill Pugh)
+						</li>
+						<li>
+							New detector to find calls to Collection.toArray() with
+							zero-length array argument; it is more efficient to pass an array
+							the size of the collection, which can be populated and returned
+							as the result (Dave Brosius)
+
+							<!-- Analysis improvements -->
+						</li>
+						<li>
+							Better suppression of false warnings in various detectors (Bill
+							Pugh, David Hovemeyer)
+						</li>
+						<li>
+							Enhancement to ReadReturnShouldBeChecked detector for skip()
+							(Dave Brosius)
+						</li>
+						<li>
+							Enhancement to DumbMethods detector (Dave Brosius)
+						</li>
+						<li>
+							Open stream detector does not report wrappers of streams passed
+							as method parameters (David Hovemeyer)
+
+							<!-- Feature enhancements -->
+						</li>
+						<li>
+							Cancel confirmation dialog in Swing GUI (Pete Angstadt)
+						</li>
+						<li>
+							Better relative path saving in Project file (Dave Brosius)
+						</li>
+						<li>
+							Detector Priority in GUI is now saved in prefs file (Dave
+							Brosius)
+						</li>
+						<li>
+							Controls in GUI to reorder source and classpath entries, and
+							ability to flip between Project details and bugs pages (Dave
+							Brosius)
+						</li>
+						<li>
+							In Swing GUI, analysis error dialog supports "Select All" and
+							"Copy" operations for easy generation of error reports (Dave
+							Brosius)
+						</li>
+						<li>
+							Complete translation of bug descriptions and messages into
+							Japanese (Hanai Shisei)
+
+							<!-- Bug fixes -->
+						</li>
+						<li>
+							Fixed bug in DroppedException detector (Dave Brosius)
+
+							<!-- Development stuff -->
+						</li>
+						<li>
+							The source distribution defaults to using JDK 1.5 javac to
+							compile, but support for compiling with JSR-14 prototype is still
+							supported
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.8.1:
+					</p>
+					<ul>
+						<li>
+							Fixed a critical ClassCastException bug (triggered if the
+							-workHard option was used, and an exception type was merged with
+							an array type during type inference)
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.8.0:
+
+					</p>
+					<ul>
+						<li>
+							Disabled SwitchFallthrough detector to work around
+							NullPointerExceptions
+						</li>
+						<li>
+							Added some additional false positive suppression heuristics
+						</li>
+					</ul>
+
+					<p>
+						Also, two contributors to the 0.8.0 release were inadvertently
+						left out of the credits:
+
+					</p>
+					<ul>
+						<li>
+							Pete Angstadt fixed several problems in the Swing GUI
+						</li>
+						<li>
+							Francis Lalonde provided a task resource file for the FindBugs
+							Ant task
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.7.4:
+
+					</p>
+					<ul>
+						<li>
+							New detector to look for uses of "+" operator to concatenate
+							String objects in a loop (Dave Brosius)
+						</li>
+						<li>
+							Reference comparison detector looks for places where the argument
+							passed to the equals(Object) method isn't the same type as the
+							receiver object
+						</li>
+						<li>
+							Better suppression of false warnings in many detectors
+						</li>
+						<li>
+							Many improvements to Eclipse plugin (Andrey Loskutov, Peter
+							Friese)
+						</li>
+						<li>
+							Fixed problem with building Eclipse plugin on Windows (Thomas
+							Klaeger)
+						</li>
+						<li>
+							Open stream detector looks for unclosed PreparedStatement objects
+							(Thomas Klaeger, Rohan Lloyd)
+						</li>
+						<li>
+							Fix for open stream detector: it wasn't detecting close() methods
+							called through an invokeinterface instruction (Thomas Klaeger)
+						</li>
+						<li>
+							Refactoring of visitor classes to enforce use of accessors for
+							visited class features (Brian Goetz)
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.7.3:
+
+					</p>
+					<ul>
+						<li>
+							Experimental modification of open stream detector to look for
+							non-escaping JDBC resources (connections and statements) that
+							aren't closed on all paths out of method
+						</li>
+						<li>
+							Eclipse plugin fixed so it compiles and runs on Eclipse 2.1.x
+							(Peter Friese)
+						</li>
+						<li>
+							Option to Swing GUI and command line to generate project file
+							using relative paths for archives, source directories, and aux
+							classpath entries (Dave Brosius)
+						</li>
+						<li>
+							Improvements to findbugs.bat script for launching FindBugs on
+							Windows (Dave Brosius)
+						</li>
+						<li>
+							Updated Japanese message translations (Hiroshi Okugawa)
+						</li>
+						<li>
+							Uncalled private methods are now reported as low priority, unless
+							they have the same name as another method in the class (which is
+							more likely to indicate an actual bug)
+						</li>
+						<li>
+							Added some missing data in the bug messages XML files
+						</li>
+						<li>
+							Fixed some problems building from source on Windows systems
+						</li>
+						<li>
+							Various minor bug fixes
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.7.2:
+
+					</p>
+					<ul>
+						<li>
+							Enhanced Eclipse plugin, which displays the detailed bug
+							description in a view (Phil Crosby)
+						</li>
+						<li>
+							Various tweaks to existing detectors to reduce false warnings
+						</li>
+						<li>
+							New command line option
+							<code>
+								-workHard
+							</code>
+							enables pruning of infeasible or unlikely exception edges, which
+							results in better accuracy in the open stream detector, at the
+							expense of a 30%-100% slowdown
+						</li>
+						<li>
+							New website and HTML documentation design
+						</li>
+						<li>
+							Documentation includes an HTML document with descriptions of all
+							bug patterns reported by FindBugs
+						</li>
+						<li>
+							Web page has a link to a
+							<a href="http://www.simeji.com/findbugs/doc/manual_ja/index.html">Japanese
+								translation</a> of the FindBugs manual, contributed by Hiroshi
+							Okugawa
+						</li>
+						<li>
+							Changed the Inconsistent Synchronization detector so that fields
+							synchronized 50% of the time (or more) are reported as medium
+							priority bugs (previously they were reported as low)
+						</li>
+						<li>
+							New detector to find code that catches
+							IllegalMonitorStateException
+						</li>
+						<li>
+							New detector to find private methods that are never called
+						</li>
+						<li>
+							New detector to find suspicious uses of non-short-circuiting
+							boolean operators (
+							<code>
+								&amp;
+							</code>
+							and
+							<code>
+								|
+							</code>
+							, rather than
+							<code>
+								&amp;&amp;
+							</code>
+							and
+							<code>
+								||
+							</code>
+							)
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.7.1:
+
+					</p>
+					<ul>
+						<li>
+							Incorporated patched version of BCEL, which allows classes
+							compiled with JDK 1.5.0 beta to be analyzed
+						</li>
+						<li>
+							Fixed some bugs related to lookups of array classes
+						</li>
+						<li>
+							Fixed bug that prevented GUI from loading XML result files when
+							running under JDK 1.5.0 beta
+						</li>
+						<li>
+							Added new experimental bug detector, LazyInit, which looks for
+							potentially buggy lazy initializations of static fields
+						</li>
+						<li>
+							Because of long filenames, switched to distributing the source
+							archive as a zip file rather than a tar file
+						</li>
+						<li>
+							The 0.7.1 source tarfile was botched - 0.7.2 has a valid source
+							archive
+						</li>
+						<li>
+							Fixed some problems in the Ant build script
+						</li>
+						<li>
+							Fixed NullPointerException when checking Class-Path attribute for
+							Jar files without manifests
+						</li>
+						<li>
+							Generate version numbers for the core and UI Eclipse plugins
+							using the Version class; all version numbers are now in a common
+							location
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.7.0:
+
+					</p>
+					<ul>
+						<li>
+							Eclipse plugin (contributed by Peter Friese)
+						</li>
+						<li>
+							Source package structure rearranged: all source (other than
+							Eclipse plugin UI) is in the edu.umd.cs.findbugs package, or a
+							subpackage
+						</li>
+						<li>
+							Class-Path attributes of manifests of analyzed jar files are used
+							to set the aux classpath automatically (Peter D. Stout)
+						</li>
+						<li>
+							GUI starts in directory specified by user.home property (Peter D.
+							Stout)
+						</li>
+						<li>
+							Added -project option to GUI (Mikko T.)
+						</li>
+						<li>
+							Added -look:{plastic,gtk,native} option to GUI, for setting look
+							and feel (Mikko T.)
+						</li>
+						<li>
+							Fixed DataflowAnalysisException in inconsistent synchronization
+							detector
+						</li>
+						<li>
+							Ant task supports failOnError parameter (Rohan Lloyd)
+						</li>
+						<li>
+							Serializable class warnings are downgraded to low priority for
+							GUI classes
+						</li>
+						<li>
+							MWN detector will only report calls to wait(), notify(), and
+							notifyAll() methods that have the correct signature
+						</li>
+						<li>
+							FindBugs works with latest CVS version of BCEL
+						</li>
+						<li>
+							Zip and Jar files may be added to the source path
+						</li>
+						<li>
+							The GUI will automatically find source files residing in analyzed
+							Zip or Jar files
+						</li>
+					</ul>
+
+					<p>
+						Note that the version number jumped from 0.6.6 to 0.6.9; there
+						were no 0.6.7 or 0.6.8 releases.
+
+					</p>
+					<p>
+						Changes since version 0.6.9:
+					</p>
+					<ul>
+						<li>
+							Added -conserveSpace option to reduce memory use at the expense
+							of analysis precision
+						</li>
+						<li>
+							Bug fixes in findbugs.bat script: JAVA_HOME handling,
+							autodetection of FINDBUGS_HOME, missing output with -textui
+						</li>
+						<li>
+							Fixed NullPointerException when a missing class is encountered
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.6.6:
+
+					</p>
+					<ul>
+						<li>
+							The null pointer dereference detector is more powerful
+						</li>
+						<li>
+							Significantly improved heuristics and bug fixes in inconsistent
+							synchronization detector
+						</li>
+						<li>
+							Improved heuristics in open stream and dropped exception
+							detectors; fewer false positives should be reported
+						</li>
+						<li>
+							Save HTML summary in XML results files, rather than recomputing;
+							this makes loading results in GUI much faster
+						</li>
+						<li>
+							Report at most one String comparison using == or != per method
+						</li>
+						<li>
+							The findbugs.bat script on Windows autodetects FINDBUGS_HOME, and
+							doesn't open a DOS window when launching the GUI (contributed by
+							TJSB)
+						</li>
+						<li>
+							Emacs reporting format (contributed by David Li)
+						</li>
+						<li>
+							Various bug fixes
+						</li>
+					</ul>
+
+					<p>
+						Changes since 0.6.5:
+
+					</p>
+					<ul>
+						<li>
+							Rewritten inconsistent synchronization detector; accuracy is
+							significantly improved, and bug reports are prioritized
+						</li>
+						<li>
+							New detector to find self assignment (x=x) of local variables
+							(suggested by Jeff Martin)
+						</li>
+						<li>
+							New detector to find calls to wait(), notify(), and notifyAll()
+							on an object which is not obviously locked
+						</li>
+						<li>
+							Open stream detector now reports Readers and Writers
+						</li>
+						<li>
+							Fixed bug in finalizer idioms detector which caused spurious
+							warnings about failure to call super.finalize() (reported by Jim
+							Menard)
+						</li>
+						<li>
+							Fixed bug where output stream was not closed using non-XML output
+							(reported by Sigiswald Madou)
+						</li>
+						<li>
+							Fixed corrupted HTML bug detail message (reported by Trevor
+							Harmon)
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.6.4:
+
+					</p>
+					<ul>
+						<li>
+							For redundant comparison of reference values, fixed false
+							positives resulting from duplication of code in finally blocks
+						</li>
+						<li>
+							Fixed false positives resulting from wrapped byte array streams
+							left open
+						</li>
+						<li>
+							Fixed bug in Ant task preventing output file from working
+							properly if a relative path was used
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.6.3:
+
+					</p>
+					<ul>
+						<li>
+							Fixed bug in Ant task where output would be corrupted, and added
+							a
+							<code>
+								timeout
+							</code>
+							attribute
+						</li>
+						<li>
+							Added -outputFile option to text UI, for explicitly specifying an
+							output file
+						</li>
+						<li>
+							GUI has a summary window, for statistics about overall bug
+							densities (contributed by Mike Fagan)
+						</li>
+						<li>
+							Find redundant comparisons of reference values
+						</li>
+						<li>
+							More accurate detection of Strings compared with == and !=
+							operators
+						</li>
+						<li>
+							Detection of other reference types which should generally not be
+							compared with == and != operators; Boolean, Integer, etc.
+						</li>
+						<li>
+							Find non-transient non-serializable instance fields in
+							Serializable classes
+						</li>
+						<li>
+							Source code may be compiled with latest early access
+							generics-enabled javac (version 2.2)
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.6.2:
+
+					</p>
+					<ul>
+						<li>
+							GUI supports filtering bugs by priority
+						</li>
+						<li>
+							Ant task rewritten; supports all functionality offered by Text UI
+							(contributed by Mike Fagan)
+						</li>
+						<li>
+							Ant task is fully documented in the manual
+						</li>
+						<li>
+							Classes in nested archives are analyzed; this allows full support
+							for analyzing .ear and .war files (contributed by Mike Fagan)
+						</li>
+						<li>
+							DepthFirstSearch changed to use non-recursive implementation;
+							this should fix the StackOverflowErrors that several users
+							reported
+						</li>
+						<li>
+							Various minor bugfixes and improvements
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.6.1:
+
+					</p>
+					<ul>
+						<li>
+							New detector to look for useless control flow (suggested by
+							Richard P. King and Mike Fagan)
+						</li>
+						<li>
+							Look for places where return value of
+							java.io.File.createNewFile() is ignored (suggested by Richard P.
+							King)
+						</li>
+						<li>
+							Fixed bug in resolution of source files (only the first source
+							directory was searched)
+						</li>
+						<li>
+							Fixed a NullPointerException in the bytecode pattern matching
+							code
+						</li>
+						<li>
+							Ant task supports project files (contributed by Mike Fagan)
+						</li>
+						<li>
+							Unix findbugs script honors the
+							<code>
+								JAVA_HOME
+							</code>
+							environment variable (contributed by Pedro Morais)
+						</li>
+						<li>
+							Allow .war and .ear files to be analyzed
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.6.0:
+
+					</p>
+					<ul>
+						<li>
+							New bug pattern detector which looks for places where a null
+							pointer might be dereferenced
+						</li>
+						<li>
+							New bug pattern detector which looks for IO streams that are
+							opened, do not escape the method, and are not closed on all paths
+							out of the method
+						</li>
+						<li>
+							New bug pattern detector to find methods that can return null
+							instead of a zero-length array
+						</li>
+						<li>
+							New bug pattern detector to find places where the == or !=
+							operators are used to compare String objects
+						</li>
+						<li>
+							Command line interface can save bugs as XML
+						</li>
+						<li>
+							GUI can save bugs to and load bugs from XML
+						</li>
+						<li>
+							An "Annotations" window in the GUI allows the user to add textual
+							annotations to bug reports; these annotations are preserved when
+							bugs are saved as XML
+						</li>
+						<li>
+							In this release, the Japanese bug summary translations by Germano
+							Leichsenring are really included (they were inadvertently omitted
+							in the previous release)
+						</li>
+						<li>
+							Completely rewrote the control flow graph builder, hopefully for
+							the last time
+						</li>
+						<li>
+							Simplified implementation of control flow graphs, which should
+							reduce memory use and possibly improve performance
+						</li>
+						<li>
+							Improvements to command line interface (list bug priorities,
+							filter by priority, specify aux classpath, specify project to
+							analyze)
+						</li>
+						<li>
+							Various bug fixes and enhancements
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.5.4
+
+					</p>
+					<ul>
+						<li>
+							Added an
+							<a href="http://ant.apache.org/">Ant</a> task for FindBugs,
+							contributed by Mike Fagan.
+						</li>
+						<li>
+							Added a GUI dialog which allows individual bug pattern detectors
+							to be enabled or disabled.&nbsp; Disabling certain slow detectors
+							can greatly speed up analysis of large programs, at the expense
+							of reducing the number of potential bugs found.
+						</li>
+						<li>
+							Added a new detector for finding improperly ignored return values
+							for methods such as
+							<code>
+								String.trim()
+							</code>
+							.&nbsp; Suggested by Andreas Mandel.
+						</li>
+						<li>
+							Japanese translations of the bug summaries, contributed by
+							Germano Leichsenring.
+						</li>
+						<li>
+							Filtering of results is supported in command line interface. See
+							the
+							<a href="manual/index.html">FindBugs manual</a> for details.
+						</li>
+						<li>
+							Added "byte code patterns", a general pattern matching
+							infrastructure for bytecode instructions.&nbsp; This feature
+							significantly reduces the complexity of implementing new bug
+							pattern detectors.
+						</li>
+						<li>
+							Enabled a new general dataflow analysis to track values in
+							methods.
+						</li>
+						<li>
+							Switched to new control-flow graph builder implementation.
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.5.3
+
+					</p>
+					<ul>
+						<li>
+							Fixed a bug in the script used to launch FindBugs on Windows
+							platforms.
+						</li>
+						<li>
+							Fixed crashes when analyzing class files without source line
+							information.
+						</li>
+						<li>
+							All major errors are reported using an error dialog; file not
+							found errors are more informative.
+						</li>
+						<li>
+							Minor GUI improvements.
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.5.2
+
+					</p>
+					<ul>
+						<li>
+							All of the source code and related files are in a single
+							directory tree.
+						</li>
+						<li>
+							Updated some of the detectors to produce source line information.
+						</li>
+						<li>
+							<a href="http://ant.apache.org/">Ant</a> build script and several
+							GUI enhancements and fixes contributed by Mike Fagan.
+						</li>
+						<li>
+							Converted to use a
+							<a href="AddingDetectors.txt">plugin architecture</a> for loading
+							bug detectors.
+						</li>
+						<li>
+							Eliminated generics-related compiler warnings.
+						</li>
+						<li>
+							More complete documentation has been added.
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.5.1:
+					</p>
+					<ul>
+						<li>
+							Fixed a large number of bugs in the BCEL Repository and
+							FindBugs's use of the Repository.&nbsp; With these changes,
+							FindBugs should
+							<em>never</em> crash or otherwise misbehave because of Repository
+							lookup failures.&nbsp; Because of these changes, you must use a
+							modified version of
+							<code>
+								bcel.jar
+							</code>
+							with FindBugs.&nbsp; This jar file is included in the FindBugs
+							0.5.2 binary release.&nbsp; A complete patch containing the
+							<a
+								href="http://faculty.ycp.edu/~dhovemey/bcel-30-April-2003.patch">modifications
+								against the BCEL CVS main branch as of April 30, 2003</a> is also
+							available.
+						</li>
+						<li>
+							Implemented the "auxiliary classpath entry list".&nbsp; Aux
+							classpath entries can be added to a project to provide classes
+							that are referenced by the analyzed application, but should not
+							themselves be analyzed.&nbsp; Having all referenced classes
+							available allows FindBugs to produce more accurate results.
+						</li>
+					</ul>
+
+					<p>
+						Changes since version 0.5.0:
+					</p>
+					<ul>
+						<li>
+							Many user interface bugs have been fixed.
+						</li>
+						<li>
+							Upgraded to a recent CVS version of BCEL, with some bug
+							fixes.&nbsp; This should prevent FindBugs from crashing when
+							there is a failure to find a class on the classpath.
+						</li>
+						<li>
+							Added support for Plastic look and feel from
+							<a href="http://www.jgoodies.com/">jgoodies.com</a>.
+						</li>
+						<li>
+							Major overhaul of infrastructure for doing dataflow analysis.
+						</li>
+					</ul>
+
+					
+<hr> <p> 
+<script language="JavaScript" type="text/javascript"> 
+<!---//hide script from old browsers 
+document.write( "Last updated "+ document.lastModified + "." ); 
+//end hiding contents ---> 
+</script> 
+<p> Send comments to <a class="sidebar" href="mailto:findbugs@cs.umd.edu">findbugs@cs.umd.edu</a> 
+<p> 
+<A href="http://sourceforge.net"><IMG src="http://sourceforge.net/sflogo.php?group_id=96405&amp;type=5" width="210" height="62" border="0" alt="SourceForge.net Logo" /></A>
+
+				</td>
+
+			</tr>
+		</table>
+
+	</body>
+
+</html>
diff --git a/doc/FAQ.html b/doc/FAQ.html
new file mode 100644
index 0000000..6e20e85
--- /dev/null
+++ b/doc/FAQ.html
@@ -0,0 +1,275 @@
+<html>
+<head>
+<title>FindBugs FAQ</title>
+<link rel="stylesheet" type="text/css" href="findbugs.css">
+
+</head>
+
+<body>
+
+<table width="100%"><tr>
+
+
+<td bgcolor="#b9b9fe" valign="top" align="left" width="20%"> 
+<table width="100%" cellspacing="0" border="0"> 
+<tr><td><a class="sidebar" href="index.html"><img src="umdFindbugs.png" alt="FindBugs"></a></td></tr> 
+
+<tr><td>&nbsp;</td></tr>
+
+<tr><td><b>Docs and Info</b></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="findbugs2.html">FindBugs 2.0</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="demo.html">Demo and data</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="users.html">Users and supporters</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="http://findbugs.blogspot.com/">FindBugs blog</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="factSheet.html">Fact sheet</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="manual/index.html">Manual</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="ja/manual/index.html">Manual(ja/&#26085;&#26412;&#35486;)</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="FAQ.html">FAQ</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="bugDescriptions.html">Bug descriptions</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="mailingLists.html">Mailing lists</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="publications.html">Documents and Publications</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="links.html">Links</a></font></td></tr> 
+
+<tr><td>&nbsp;</td></tr>
+
+<tr><td><a class="sidebar" href="downloads.html"><b>Downloads</b></a></td></tr> 
+
+<tr><td>&nbsp;</td></tr>
+
+<tr><td><a class="sidebar" href="http://www.cafeshops.com/findbugs"><b>FindBugs Swag</b></a></td></tr>
+
+<tr><td>&nbsp;</td></tr>
+
+<tr><td><b>Development</b></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="http://sourceforge.net/tracker/?group_id=96405">Open bugs</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="reportingBugs.html">Reporting bugs</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="contributing.html">Contributing</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="team.html">Dev team</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="api/index.html">API</a> <a class="sidebar" href="api/overview-summary.html">[no frames]</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="Changes.html">Change log</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="http://sourceforge.net/projects/findbugs">SF project page</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="http://code.google.com/p/findbugs/source/browse/">Browse source</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="http://code.google.com/p/findbugs/source/list">Latest code changes</a></font></td></tr> 
+</table> 
+</td>
+
+<td>
+<h1>FindBugs FAQ</h1>
+
+<p> This document contains answers to frequently asked questions about
+<a href="index.html">FindBugs</a>.&nbsp; If you just want general
+information about FindBugs, have a look at the
+<a href="factSheet.html">fact sheet</a> and the
+<a href="manual/index.html">manual</a>.
+
+<h2>Contents</h2>
+<ol>
+<li> <a href="#q1">I'm getting java.lang.UnsupportedClassVersionError when I try to run FindBugs</a>
+<li> <a href="#q2">When I click the "Find Bugs!" button, I get a NoSuchMethodError or VerifyError</a>
+<li> <a href="#q3">FindBugs is running out of memory, or is taking a long time to finish</a>
+<li> <a href="#q4">What is the "auxiliary classpath"?  Why should I specify it?</a>
+<li> <a href="#q5">The Eclipse plugin doesn't load</a>
+<li> <a href="#q6">I'm getting a lot of false "OS" and "ODR" warnings</a>
+<li> <a href="#q7">The Eclipse plugin loads, but doesn't work correctly</a>
+<li> <a href="#q8">Where is the Maven plugin for FindBugs?</a>
+<li> <a href="#q9">Where is the NetBeans plugin for FindBugs?</a>
+</ol>
+
+<h2><a name="q1">Q1: I'm getting java.lang.UnsupportedClassVersionError when I try to run FindBugs</a></h2>
+
+<p> FindBugs requires JRE 1.5.0 or later to run.&nbsp; If you use an earlier version,
+you will see an exception error message similar to the following:
+<pre>
+Exception in thread "main" java.lang.UnsupportedClassVersionError:
+edu/umd/cs/findbugs/gui/FindBugsFrame (Unsupported major.minor version 48.0)
+</pre>
+The solution is to upgrade to JRE 1.5.0 or later.
+
+<h2><a name="q2">Q2: When I click the "Find Bugs!" button, I get a NoSuchMethodError or VerifyError</a></h2>
+
+<p> The symptom of this bug is that when you start the FindBugs analysis,
+you see an exception similar to the following:
+<pre>
+java.lang.NoSuchMethodError: org.apache.bcel.Repository.setRepository(Lorg/apache/bcel/util/Repository;)V
+        at edu.umd.cs.findbugs.FindBugs.clearRepository(FindBugs.java:483)
+        ...
+</pre>
+
+or
+
+<pre>
+java.lang.VerifyError: Cannot inherit from final class
+	at java.lang.ClassLoader.defineClass0(Native Method)
+	at java.lang.ClassLoader.defineClass(ClassLoader.java:537)
+	...
+</pre>
+
+<p> The problem here is that the wrong version of the
+<a href="http://jakarta.apache.org/bcel/">Apache BCEL</a>
+library is being found.&nbsp; FindBugs requires its own
+version of BCEL, which normally will be used automatically
+when you invoke the <code>findbugs</code> or <code>findbugs.bat</code>
+scripts used to launch FindBugs.&nbsp; If an old version of BCEL is installed
+in a location, such as "lib/endorsed" in the JRE installation,
+where it overrides classes on the application classpath,
+FindBugs will not execute properly.&nbsp;
+We know of several reasons this could happen
+
+<ul>
+<li> If you install the
+<a href="http://java.sun.com/webservices/downloads/webservicespack.html">Java(TM) Web Services
+Developer Pack 1.2</a>
+in the <code>lib/endorsed</code> directory of your Java Runtime Environment (JRE).&nbsp;
+The file <code>xsltc.jar</code> contains an old version of BCEL that is incompatible with
+FindBugs.&nbsp;
+
+<li> Another possibility is that you are using the IBM JDK.&nbsp;
+Some versions include a version of BCEL which conflicts with the
+one required by FindBugs.&nbsp; This problem is fixed in version 1.4.1 SP1,
+so upgrading your JDK should allow FindBugs to run correctly.
+
+<li> Some versions of the Apache Xalan XSLT processor include
+an old version of BCEL in <code>xalan.jar</code>.
+
+</ul>
+
+<p> In all of these cases, you should be able to run FindBugs
+by either removing the offending version of BCEL from your JRE,
+or installing a clean JRE or JDK and using that to run FindBugs.
+
+<p> Many thanks to Peter Meulmeester, Michael Levi, and Thomas Klaeger
+for providing information on this problem.
+
+<h2><a name="q3">Q3: FindBugs is running out of memory, or is taking a long time to finish</a></h2>
+
+<p> In general, FindBugs requires lots of memory and a relatively
+fast CPU.  For large applications, 512M or more of heap space may be
+required.  By default, FindBugs allocates 256M of heap space.
+You can increase this using the <code>-maxHeap <i>n</i></code> option,
+where <i>n</i> is the number of megabytes of heap space to allocate.
+
+
+<h2><a name="q4">Q4: What is the "auxiliary classpath"?  Why should I specify it?</a></h2>
+
+<p> Many important facts about a Java class require information about
+the classes that it references.&nbsp; For example:
+<ul>
+<li> What other classes and interfaces the class inherits from
+<li> What exceptions can be thrown by methods in external classes
+and interfaces
+</ul>
+
+<p> The "auxiliary classpath" is a list of Jar files, directories, and
+class files containing classes that are <em>used</em> by the code you
+want FindBugs to analyze, but should not themselves be analyzed
+by FindBugs.
+
+<p> If FindBugs doesn't have complete information about referenced classes,
+it will not be able to produce results that are as accurate as possible.&nbsp;
+For example, having a complete repository of referenced classes allows
+FindBugs to prune control flow information so it can concentrate on
+paths through methods that are most likely to be feasible at runtime.&nbsp;
+Also, some bug detectors (such as the suspicious reference comparison detector)
+rely on being able to perform type inference, which requires complete
+type hierarchy information.
+
+<p> For these reasons, we strongly recommend that you completely specify
+the auxiliary classpath when you run FindBugs.&nbsp; You can do this
+by using the <code>-auxclasspath</code> command line option, or the
+"Classpath entries" list in the GUI project editor dialog.
+
+<p> If FindBugs cannot find a class referenced by your application, it
+will print out a message when the analysis completes, specifying the
+classes that were missing.&nbsp; You should modify the auxiliary classpath
+to specify how to find the missing classes, and then run FindBugs again.
+
+<h2><a name="q5">Q5: The Eclipse plugin doesn't load</a></h2>
+
+<p> The symptom of this problem is that Eclipse fails to load
+the FindBugs UI plugin with the message:
+<blockquote>
+Plug-in "edu.umd.cs.findbugs.plugin.eclipse" was disabled due to missing or disabled
+prerequisite plug-in "org.eclipse.ui.ide"
+</blockquote>
+
+<p> The reason for this problem is that the Eclipse
+plugin distributed with FindBugs
+does not work with 2.x versions of Eclipse.
+Please use Eclipse version 3.3 (June 2007) or newer.
+
+<h2><a name="q6">Q6: I'm getting a lot of false "OS" and "ODR" warnings</a></h2>
+
+<p> By default, FindBugs assumes that any method invocation can
+throw an unchecked runtime exception.&nbsp; As a result,
+it may assume that an unchecked exception thrown out of the
+method could bypass a call to a <code>close()</code> method
+for a stream or database resource.
+
+<p> You can use the <code>-workHard</code> command line argument
+or the <code>findbugs.workHard</code> boolean analysis property
+to make FindBugs work harder to prune unlikely exception
+edges.&nbsp; This generally reduces the number of
+false warnings, at the expense of slowing down the
+analysis.
+
+<h2><a name="q7">Q7: The Eclipse plugin loads, but doesn't work correctly</a></h2>
+
+<p> In versions 0.0.6 and 0.0.7 of the FindBugs Eclipse plugin,
+which correspond to the 0.7.4 and 0.8.0 releases,
+bugs in the experimental SwitchFallthrough detector can prevent
+FindBugs from running properly within Eclipse.
+
+<p> To work around the problem, make sure that SwitchFallthrough
+is disabled in the FindBugs Properties of your project.&nbsp;
+Right click on your project, and choose "Properties".&nbsp;
+In the Properties dialog, choose "FindBugs",
+and disable the checkbox next to SwitchFallthrough.
+
+<p> Another common problem with the Eclipse plugin is that
+the FindBugs warnings do not appear in the "Problems" view.&nbsp;
+Make sure that FindBugs warnings are enabled in the filters
+for this view.&nbsp; The Filters menu is accessible by
+clicking on the icon that looks like this:
+<blockquote>
+<img src="eclipse-filters-icon.png">
+</blockquote>
+Make sure the "FindBugs Problem" checkbox is enabled.
+
+<h2><a name="q8">Q8: Where is the Maven plugin for FindBugs?</a></h2>
+
+<p>
+The <a href="http://maven.apache.org/">Maven</a> Plugin for FindBugs
+may be found <a href="http://mojo.codehaus.org/findbugs-maven-plugin/">here</a>.&nbsp;
+Please note that the Maven plugin is not maintained by the FindBugs developers,
+so we can't answer questions about it.
+</p>
+
+<h2><a name="q9">Q9: Where is the NetBeans plugin for FindBugs?</a></h2>
+
+<p>We recommend <a href="http://kenai.com/projects/sqe/pages/Home">SQE: Software Quality Environment</a>
+which bundles FindBugs, PMD and CheckStyle. Use the following
+update site:
+<a href="http://deadlock.netbeans.org/hudson/job/sqe/lastStableBuild/artifact/build/full-sqe-updatecenter/updates.xml
+">http://deadlock.netbeans.org/hudson/job/sqe/lastStableBuild/artifact/build/full-sqe-updatecenter/updates.xml</a>a>
+<p>Pease note that the SQE plugin is not maintained by the FindBugs developers,
+so we can't answer questions about it.
+</p>
+
+
+<hr> <p> 
+<script language="JavaScript" type="text/javascript"> 
+<!---//hide script from old browsers 
+document.write( "Last updated "+ document.lastModified + "." ); 
+//end hiding contents ---> 
+</script> 
+<p> Send comments to <a class="sidebar" href="mailto:findbugs@cs.umd.edu">findbugs@cs.umd.edu</a> 
+<p> 
+<A href="http://sourceforge.net"><IMG src="http://sourceforge.net/sflogo.php?group_id=96405&amp;type=5" width="210" height="62" border="0" alt="SourceForge.net Logo" /></A>
+
+</td>
+
+</table>
+
+</body>
+
+</html>
diff --git a/doc/FilterFile.txt b/doc/FilterFile.txt
new file mode 100644
index 0000000..1fed032
--- /dev/null
+++ b/doc/FilterFile.txt
@@ -0,0 +1,125 @@
+=============
+How it works:
+=============
+
+A filter file is an XML file with a top-level "FindBugsFilter" element
+which has some number of "Match" elements as children.  Each Match
+element represents a predicate which is applied to generated bug instances.
+Usually, a filter will be used to exclude bug instances.  For example:
+
+  findbugs -textui -exclude myExcludeFilter.xml myApp.jar
+
+However, a filter could also be used to select bug instances to specifically
+report:
+
+  findbugs -textui -include myIncludeFilter.xml myApp.jar
+
+Match has "class" and "classregex" attributes specifying what class or classes
+the predicate applies to.
+
+Match contains children, which are conjuncts of the predicate.
+(I.e., each of the children must be true for the predicate to be true.)
+
+=======================
+Types of Match clauses:
+=======================
+
+   <BugCode> specifies abbreviations of bugs.
+   The "name" attribute is a comma-seperated list of abbreviations.
+
+   <Method> specifies a method.  The "name" attribute is the name
+   of the method.  The "params" attribute is a comma separated list
+   of the types of the method's parameters.  The "returns" attribute is
+   the method's return type.  In "params" and "returns", class names
+   must be fully qualified.  (E.g., "java.lang.String" instead of just
+   "String".)  Note that "params" and "returns" are optional; you can
+   just specify "name", and the clause will match all methods with
+   that name.  However, if you specify either "params" or "returns",
+   you must specify both of them.
+
+   <Or> combines Match clauses as disjuncts.  I.e., you can put two
+   "Method" elements in an Or clause in order match either method.
+
+========
+Caveats:
+========
+
+Match clauses can only match information that is actually contained in the
+bug instances.  Every bug instance has a class, so in general, excluding
+bugs by class will work.
+
+Some bug instances have two classes.  For example, the DE (dropped exception)
+bugs report both the class containing the method where the dropped exception
+happens, and the class which represents the type of the dropped exception.
+Only the FIRST (primary) class is matched against Match clauses.
+So, for example, if you want to suppress IC (initialization circularity)
+reports for classes "com.foobar.A" and "com.foobar.B", you would use
+two Match clauses:
+
+   <Match class="com.foobar.A">
+      <BugCode name="IC" />
+   </Match>
+
+   <Match class="com.foobar.B">
+      <BugCode name="IC" />
+   </Match>
+
+Many kinds of bugs report what method they occur in.  For those bug instances,
+you can put Method clauses in the Match element and they should work
+as expected.
+
+=========
+Examples:
+=========
+
+  1. Match all bug reports for a class.
+
+     <Match class="com.foobar.MyClass" />
+
+  2. Match certain tests from a class.
+     <Match class="com.foobar.MyClass">
+       <BugCode name="DE,UrF,SIC" />
+     </Match>
+
+  3. Match certain tests from all classes.
+
+     <Match classregex=".*" >
+       <BugCode name="DE,UrF,SIC" />
+     </Match>
+
+  4. Match bug types from specified methods of a class.
+
+     <Match class="com.foobar.MyClass">
+       <Or>
+         <Method name="frob" params="int,java.lang.String" returns="void" />
+         <Method name="blat" params="" returns="boolean" />
+       </Or>
+       <BugCode name="DC" />
+     </Match>
+
+=================
+Complete Example:
+=================
+
+<FindBugsFilter>
+     <Match class="com.foobar.ClassNotToBeAnalyzed" />
+
+     <Match class="com.foobar.ClassWithSomeBugsMatched">
+       <BugCode name="DE,UrF,SIC" />
+     </Match>
+
+     <!-- Match all XYZ violations. -->
+     <Match classregex=".*" >
+       <BugCode name="XYZ" />
+     </Match>
+
+     <!-- Match all doublecheck violations in these methods of "AnotherClass". -->
+     <Match class="com.foobar.AnotherClass">
+       <Or>
+         <Method name="nonOverloadedMethod" />
+         <Method name="frob" params="int,java.lang.String" returns="void" />
+         <Method name="blat" params="" returns="boolean" />
+       </Or>
+       <BugCode name="DC" />
+     </Match>
+</FindBugsFilter>
diff --git a/doc/allBugDescriptions.html b/doc/allBugDescriptions.html
new file mode 100644
index 0000000..f1cf159
--- /dev/null
+++ b/doc/allBugDescriptions.html
@@ -0,0 +1,5285 @@
+<html><head><title>FindBugs Bug Descriptions (Unabridged)</title>
+<link rel="stylesheet" type="text/css" href="findbugs.css"/>
+<link rel="shortcut icon" href="favicon.ico" type="image/x-icon"/>
+</head><body>
+
+<table width="100%"><tr>
+
+<td bgcolor="#b9b9fe" valign="top" align="left" width="20%"> 
+<table width="100%" cellspacing="0" border="0"> 
+<tr><td><a class="sidebar" href="index.html"><img src="umdFindbugs.png" alt="FindBugs"></a></td></tr> 
+
+<tr><td>&nbsp;</td></tr>
+
+<tr><td><b>Docs and Info</b></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="findbugs2.html">FindBugs 2.0</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="demo.html">Demo and data</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="users.html">Users and supporters</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="http://findbugs.blogspot.com/">FindBugs blog</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="factSheet.html">Fact sheet</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="manual/index.html">Manual</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="ja/manual/index.html">Manual(ja/&#26085;&#26412;&#35486;)</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="FAQ.html">FAQ</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="bugDescriptions.html">Bug descriptions</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="mailingLists.html">Mailing lists</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="publications.html">Documents and Publications</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="links.html">Links</a></font></td></tr> 
+
+<tr><td>&nbsp;</td></tr>
+
+<tr><td><a class="sidebar" href="downloads.html"><b>Downloads</b></a></td></tr> 
+
+<tr><td>&nbsp;</td></tr>
+
+<tr><td><a class="sidebar" href="http://www.cafeshops.com/findbugs"><b>FindBugs Swag</b></a></td></tr>
+
+<tr><td>&nbsp;</td></tr>
+
+<tr><td><b>Development</b></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="http://sourceforge.net/tracker/?group_id=96405">Open bugs</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="reportingBugs.html">Reporting bugs</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="contributing.html">Contributing</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="team.html">Dev team</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="api/index.html">API</a> <a class="sidebar" href="api/overview-summary.html">[no frames]</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="Changes.html">Change log</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="http://sourceforge.net/projects/findbugs">SF project page</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="http://code.google.com/p/findbugs/source/browse/">Browse source</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="http://code.google.com/p/findbugs/source/list">Latest code changes</a></font></td></tr> 
+</table> 
+</td>
+<td align="left" valign="top">
+<h1>FindBugs Bug Descriptions (Unabridged)</h1>
+<p>This document lists all of the bug patterns reported by the
+latest development version of 
+<a href="http://findbugs.sourceforge.net">FindBugs</a>.&nbsp; Note that this may include
+bug patterns not available in any released version of FindBugs,
+as well as bug patterns that are not enabled by default.
+<h2>Summary</h2>
+<table width="100%">
+<tr bgcolor="#b9b9fe"><th>Description</th><th>Category</th></tr>
+<tr bgcolor="#eeeeee"><td><a href="#AM_CREATES_EMPTY_JAR_FILE_ENTRY">AM: Creates an empty jar file entry</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#AM_CREATES_EMPTY_ZIP_FILE_ENTRY">AM: Creates an empty zip file entry</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#BC_EQUALS_METHOD_SHOULD_WORK_FOR_ALL_OBJECTS">BC: Equals method should not assume anything about the type of its argument</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#BIT_SIGNED_CHECK">BIT: Check for sign of bitwise operation</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#CN_IDIOM">CN: Class implements Cloneable but does not define or use clone method</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#CN_IDIOM_NO_SUPER_CALL">CN: clone method does not call super.clone()</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#CN_IMPLEMENTS_CLONE_BUT_NOT_CLONEABLE">CN: Class defines clone() but doesn't implement Cloneable</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#CO_ABSTRACT_SELF">Co: Abstract class defines covariant compareTo() method</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#CO_SELF_NO_OBJECT">Co: Covariant compareTo() method defined</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DE_MIGHT_DROP">DE: Method might drop exception</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DE_MIGHT_IGNORE">DE: Method might ignore exception</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DMI_ENTRY_SETS_MAY_REUSE_ENTRY_OBJECTS">DMI: Adding elements of an entry set may fail due to reuse of Entry objects</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DMI_RANDOM_USED_ONLY_ONCE">DMI: Random object created and used only once</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DMI_USING_REMOVEALL_TO_CLEAR_COLLECTION">DMI: Don't use removeAll to clear a collection</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DM_EXIT">Dm: Method invokes System.exit(...)</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DM_RUN_FINALIZERS_ON_EXIT">Dm: Method invokes dangerous method runFinalizersOnExit</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#ES_COMPARING_PARAMETER_STRING_WITH_EQ">ES: Comparison of String parameter using == or !=</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#ES_COMPARING_STRINGS_WITH_EQ">ES: Comparison of String objects using == or !=</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#EQ_ABSTRACT_SELF">Eq: Abstract class defines covariant equals() method</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#EQ_CHECK_FOR_OPERAND_NOT_COMPATIBLE_WITH_THIS">Eq: Equals checks for incompatible operand</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#EQ_COMPARETO_USE_OBJECT_EQUALS">Eq: Class defines compareTo(...) and uses Object.equals()</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#EQ_GETCLASS_AND_CLASS_CONSTANT">Eq: equals method fails for subtypes</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#EQ_SELF_NO_OBJECT">Eq: Covariant equals() method defined</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#FI_EMPTY">FI: Empty finalizer should be deleted</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#FI_EXPLICIT_INVOCATION">FI: Explicit invocation of finalizer</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#FI_FINALIZER_NULLS_FIELDS">FI: Finalizer nulls fields</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#FI_FINALIZER_ONLY_NULLS_FIELDS">FI: Finalizer only nulls fields</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#FI_MISSING_SUPER_CALL">FI: Finalizer does not call superclass finalizer</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#FI_NULLIFY_SUPER">FI: Finalizer nullifies superclass finalizer</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#FI_USELESS">FI: Finalizer does nothing but call superclass finalizer</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#VA_FORMAT_STRING_USES_NEWLINE">FS: Format string should use %n rather than \n</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#GC_UNCHECKED_TYPE_IN_GENERIC_CALL">GC: Unchecked type in generic call</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#HE_EQUALS_NO_HASHCODE">HE: Class defines equals() but not hashCode()</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#HE_EQUALS_USE_HASHCODE">HE: Class defines equals() and uses Object.hashCode()</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#HE_HASHCODE_NO_EQUALS">HE: Class defines hashCode() but not equals()</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#HE_HASHCODE_USE_OBJECT_EQUALS">HE: Class defines hashCode() and uses Object.equals()</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#HE_INHERITS_EQUALS_USE_HASHCODE">HE: Class inherits equals() and uses Object.hashCode()</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#IC_SUPERCLASS_USES_SUBCLASS_DURING_INITIALIZATION">IC: Superclass uses subclass during initialization</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#IMSE_DONT_CATCH_IMSE">IMSE: Dubious catching of IllegalMonitorStateException</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#ISC_INSTANTIATE_STATIC_CLASS">ISC: Needless instantiation of class that only supplies static methods</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#IT_NO_SUCH_ELEMENT">It: Iterator next() method can't throw NoSuchElementException</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#J2EE_STORE_OF_NON_SERIALIZABLE_OBJECT_INTO_SESSION">J2EE: Store of non serializable object into HttpSession</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#JCIP_FIELD_ISNT_FINAL_IN_IMMUTABLE_CLASS">JCIP: Fields of immutable classes should be final</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NP_BOOLEAN_RETURN_NULL">NP: Method with Boolean return type returns explicit null</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NP_CLONE_COULD_RETURN_NULL">NP: Clone method may return null</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NP_EQUALS_SHOULD_HANDLE_NULL_ARGUMENT">NP: equals() method does not check for null argument</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NP_TOSTRING_COULD_RETURN_NULL">NP: toString method may return null</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NM_CLASS_NAMING_CONVENTION">Nm: Class names should start with an upper case letter</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NM_CLASS_NOT_EXCEPTION">Nm: Class is not derived from an Exception, even though it is named as such</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NM_CONFUSING">Nm: Confusing method names</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NM_FIELD_NAMING_CONVENTION">Nm: Field names should start with a lower case letter</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NM_FUTURE_KEYWORD_USED_AS_IDENTIFIER">Nm: Use of identifier that is a keyword in later versions of Java</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NM_FUTURE_KEYWORD_USED_AS_MEMBER_IDENTIFIER">Nm: Use of identifier that is a keyword in later versions of Java</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NM_METHOD_NAMING_CONVENTION">Nm: Method names should start with a lower case letter</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NM_SAME_SIMPLE_NAME_AS_INTERFACE">Nm: Class names shouldn't shadow simple name of implemented interface</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NM_SAME_SIMPLE_NAME_AS_SUPERCLASS">Nm: Class names shouldn't shadow simple name of superclass</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NM_VERY_CONFUSING_INTENTIONAL">Nm: Very confusing method names (but perhaps intentional)</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NM_WRONG_PACKAGE_INTENTIONAL">Nm: Method doesn't override method in superclass due to wrong package for parameter</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#ODR_OPEN_DATABASE_RESOURCE">ODR: Method may fail to close database resource</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#ODR_OPEN_DATABASE_RESOURCE_EXCEPTION_PATH">ODR: Method may fail to close database resource on exception</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#OS_OPEN_STREAM">OS: Method may fail to close stream</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#OS_OPEN_STREAM_EXCEPTION_PATH">OS: Method may fail to close stream on exception</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#PZ_DONT_REUSE_ENTRY_OBJECTS_IN_ITERATORS">PZ: Don't reuse entry objects in iterators</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#RC_REF_COMPARISON_BAD_PRACTICE">RC: Suspicious reference comparison to constant</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#RC_REF_COMPARISON_BAD_PRACTICE_BOOLEAN">RC: Suspicious reference comparison of Boolean values</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#RR_NOT_CHECKED">RR: Method ignores results of InputStream.read()</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SR_NOT_CHECKED">RR: Method ignores results of InputStream.skip()</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#RV_NEGATING_RESULT_OF_COMPARETO">RV: Negating the result of compareTo()/compare()</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#RV_RETURN_VALUE_IGNORED_BAD_PRACTICE">RV: Method ignores exceptional return value</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#SI_INSTANCE_BEFORE_FINALS_ASSIGNED">SI: Static initializer creates instance before all static final fields assigned</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SW_SWING_METHODS_INVOKED_IN_SWING_THREAD">SW: Certain swing methods needs to be invoked in Swing thread</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#SE_BAD_FIELD">Se: Non-transient non-serializable instance field in serializable class</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SE_BAD_FIELD_INNER_CLASS">Se: Non-serializable class has a serializable inner class</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#SE_BAD_FIELD_STORE">Se: Non-serializable value stored into instance field of a serializable class</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SE_COMPARATOR_SHOULD_BE_SERIALIZABLE">Se: Comparator doesn't implement Serializable</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#SE_INNER_CLASS">Se: Serializable inner class</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SE_NONFINAL_SERIALVERSIONID">Se: serialVersionUID isn't final</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#SE_NONLONG_SERIALVERSIONID">Se: serialVersionUID isn't long</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SE_NONSTATIC_SERIALVERSIONID">Se: serialVersionUID isn't static</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#SE_NO_SUITABLE_CONSTRUCTOR">Se: Class is Serializable but its superclass doesn't define a void constructor</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SE_NO_SUITABLE_CONSTRUCTOR_FOR_EXTERNALIZATION">Se: Class is Externalizable but doesn't define a void constructor</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#SE_READ_RESOLVE_MUST_RETURN_OBJECT">Se: The readResolve method must be declared with a return type of Object. </a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SE_TRANSIENT_FIELD_NOT_RESTORED">Se: Transient field that isn't set by deserialization. </a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#SE_NO_SERIALVERSIONID">SnVI: Class is Serializable, but doesn't define serialVersionUID</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#UI_INHERITANCE_UNSAFE_GETRESOURCE">UI: Usage of GetResource may be unsafe if class is extended</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#BC_IMPOSSIBLE_CAST">BC: Impossible cast</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#BC_IMPOSSIBLE_DOWNCAST">BC: Impossible downcast</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#BC_IMPOSSIBLE_DOWNCAST_OF_TOARRAY">BC: Impossible downcast of toArray() result</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#BC_IMPOSSIBLE_INSTANCEOF">BC: instanceof will always return false</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#BIT_ADD_OF_SIGNED_BYTE">BIT: Bitwise add of signed byte value</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#BIT_AND">BIT: Incompatible bit masks</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#BIT_AND_ZZ">BIT: Check to see if ((...) & 0) == 0</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#BIT_IOR">BIT: Incompatible bit masks</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#BIT_IOR_OF_SIGNED_BYTE">BIT: Bitwise OR of signed byte value</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#BIT_SIGNED_CHECK_HIGH_BIT">BIT: Check for sign of bitwise operation</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#BOA_BADLY_OVERRIDDEN_ADAPTER">BOA: Class overrides a method implemented in super class Adapter wrongly</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#ICAST_BAD_SHIFT_AMOUNT">BSHIFT: 32 bit int shifted by an amount not in the range 0..31</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#BX_UNBOXED_AND_COERCED_FOR_TERNARY_OPERATOR">Bx: Primitive value is unboxed and coerced for ternary operator</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#CO_COMPARETO_RESULTS_MIN_VALUE">Co: compareTo()/compare() returns Integer.MIN_VALUE</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DLS_DEAD_STORE_OF_CLASS_LITERAL">DLS: Dead store of class literal</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DLS_OVERWRITTEN_INCREMENT">DLS: Overwritten increment</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DMI_ARGUMENTS_WRONG_ORDER">DMI: Reversed method arguments</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DMI_BAD_MONTH">DMI: Bad constant value for month</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DMI_BIGDECIMAL_CONSTRUCTED_FROM_DOUBLE">DMI: BigDecimal constructed from double that isn't represented precisely</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DMI_CALLING_NEXT_FROM_HASNEXT">DMI: hasNext method invokes next</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DMI_COLLECTIONS_SHOULD_NOT_CONTAIN_THEMSELVES">DMI: Collections should not contain themselves</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DMI_DOH">DMI: D'oh! A nonsensical method invocation</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DMI_INVOKING_HASHCODE_ON_ARRAY">DMI: Invocation of hashCode on an array</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DMI_LONG_BITS_TO_DOUBLE_INVOKED_ON_INT">DMI: Double.longBitsToDouble invoked on an int</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DMI_VACUOUS_SELF_COLLECTION_CALL">DMI: Vacuous call to collections</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DMI_ANNOTATION_IS_NOT_VISIBLE_TO_REFLECTION">Dm: Can't use reflection to check for presence of annotation without runtime retention</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DMI_FUTILE_ATTEMPT_TO_CHANGE_MAXPOOL_SIZE_OF_SCHEDULED_THREAD_POOL_EXECUTOR">Dm: Futile attempt to change max pool size of ScheduledThreadPoolExecutor</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DMI_SCHEDULED_THREAD_POOL_EXECUTOR_WITH_ZERO_CORE_THREADS">Dm: Creation of ScheduledThreadPoolExecutor with zero core threads</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DMI_VACUOUS_CALL_TO_EASYMOCK_METHOD">Dm: Useless/vacuous call to EasyMock method</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#EC_ARRAY_AND_NONARRAY">EC: equals() used to compare array and nonarray</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#EC_BAD_ARRAY_COMPARE">EC: Invocation of equals() on an array, which is equivalent to ==</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#EC_INCOMPATIBLE_ARRAY_COMPARE">EC: equals(...) used to compare incompatible arrays</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#EC_NULL_ARG">EC: Call to equals(null)</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#EC_UNRELATED_CLASS_AND_INTERFACE">EC: Call to equals() comparing unrelated class and interface</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#EC_UNRELATED_INTERFACES">EC: Call to equals() comparing different interface types</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#EC_UNRELATED_TYPES">EC: Call to equals() comparing different types</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#EC_UNRELATED_TYPES_USING_POINTER_EQUALITY">EC: Using pointer equality to compare different types</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#EQ_ALWAYS_FALSE">Eq: equals method always returns false</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#EQ_ALWAYS_TRUE">Eq: equals method always returns true</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#EQ_COMPARING_CLASS_NAMES">Eq: equals method compares class names rather than class objects</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#EQ_DONT_DEFINE_EQUALS_FOR_ENUM">Eq: Covariant equals() method defined for enum</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#EQ_OTHER_NO_OBJECT">Eq: equals() method defined that doesn't override equals(Object)</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#EQ_OTHER_USE_OBJECT">Eq: equals() method defined that doesn't override Object.equals(Object)</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#EQ_OVERRIDING_EQUALS_NOT_SYMMETRIC">Eq: equals method overrides equals in superclass and may not be symmetric</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#EQ_SELF_USE_OBJECT">Eq: Covariant equals() method defined, Object.equals(Object) inherited</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#FE_TEST_IF_EQUAL_TO_NOT_A_NUMBER">FE: Doomed test for equality to NaN</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#VA_FORMAT_STRING_BAD_ARGUMENT">FS: Format string placeholder incompatible with passed argument</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#VA_FORMAT_STRING_BAD_CONVERSION">FS: The type of a supplied argument doesn't match format specifier</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#VA_FORMAT_STRING_EXPECTED_MESSAGE_FORMAT_SUPPLIED">FS: MessageFormat supplied where printf style format expected</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#VA_FORMAT_STRING_EXTRA_ARGUMENTS_PASSED">FS: More arguments are passed than are actually used in the format string</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#VA_FORMAT_STRING_ILLEGAL">FS: Illegal format string</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#VA_FORMAT_STRING_MISSING_ARGUMENT">FS: Format string references missing argument</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#VA_FORMAT_STRING_NO_PREVIOUS_ARGUMENT">FS: No previous argument for format string</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#GC_UNRELATED_TYPES">GC: No relationship between generic parameter and method argument</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#HE_SIGNATURE_DECLARES_HASHING_OF_UNHASHABLE_CLASS">HE: Signature declares use of unhashable class in hashed construct</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#HE_USE_OF_UNHASHABLE_CLASS">HE: Use of class without a hashCode() method in a hashed data structure</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#ICAST_INT_2_LONG_AS_INSTANT">ICAST: int value converted to long and used as absolute time</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#ICAST_INT_CAST_TO_DOUBLE_PASSED_TO_CEIL">ICAST: integral value cast to double and then passed to Math.ceil</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#ICAST_INT_CAST_TO_FLOAT_PASSED_TO_ROUND">ICAST: int value cast to float and then passed to Math.round</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#IJU_ASSERT_METHOD_INVOKED_FROM_RUN_METHOD">IJU: JUnit assertion in run method will not be noticed by JUnit</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#IJU_BAD_SUITE_METHOD">IJU: TestCase declares a bad suite method </a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#IJU_NO_TESTS">IJU: TestCase has no tests</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#IJU_SETUP_NO_SUPER">IJU: TestCase defines setUp that doesn't call super.setUp()</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#IJU_SUITE_NOT_STATIC">IJU: TestCase implements a non-static suite method </a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#IJU_TEARDOWN_NO_SUPER">IJU: TestCase defines tearDown that doesn't call super.tearDown()</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#IL_CONTAINER_ADDED_TO_ITSELF">IL: A collection is added to itself</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#IL_INFINITE_LOOP">IL: An apparent infinite loop</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#IL_INFINITE_RECURSIVE_LOOP">IL: An apparent infinite recursive loop</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#IM_MULTIPLYING_RESULT_OF_IREM">IM: Integer multiply of result of integer remainder</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#INT_BAD_COMPARISON_WITH_INT_VALUE">INT: Bad comparison of int value with long constant</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#INT_BAD_COMPARISON_WITH_NONNEGATIVE_VALUE">INT: Bad comparison of nonnegative value with negative constant</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#INT_BAD_COMPARISON_WITH_SIGNED_BYTE">INT: Bad comparison of signed byte</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#IO_APPENDING_TO_OBJECT_OUTPUT_STREAM">IO: Doomed attempt to append to an object output stream</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#IP_PARAMETER_IS_DEAD_BUT_OVERWRITTEN">IP: A parameter is dead upon entry to a method but overwritten</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#MF_CLASS_MASKS_FIELD">MF: Class defines field that masks a superclass field</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#MF_METHOD_MASKS_FIELD">MF: Method defines a variable that obscures a field</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NP_ALWAYS_NULL">NP: Null pointer dereference</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NP_ALWAYS_NULL_EXCEPTION">NP: Null pointer dereference in method on exception path</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NP_ARGUMENT_MIGHT_BE_NULL">NP: Method does not check for null argument</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NP_CLOSING_NULL">NP: close() invoked on a value that is always null</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NP_GUARANTEED_DEREF">NP: Null value is guaranteed to be dereferenced</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NP_GUARANTEED_DEREF_ON_EXCEPTION_PATH">NP: Value is null and guaranteed to be dereferenced on exception path</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NP_NONNULL_FIELD_NOT_INITIALIZED_IN_CONSTRUCTOR">NP: Nonnull field is not initialized</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NP_NONNULL_PARAM_VIOLATION">NP: Method call passes null to a nonnull parameter </a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NP_NONNULL_RETURN_VIOLATION">NP: Method may return null, but is declared @NonNull</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NP_NULL_INSTANCEOF">NP: A known null value is checked to see if it is an instance of a type</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NP_NULL_ON_SOME_PATH">NP: Possible null pointer dereference</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NP_NULL_ON_SOME_PATH_EXCEPTION">NP: Possible null pointer dereference in method on exception path</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NP_NULL_PARAM_DEREF">NP: Method call passes null for nonnull parameter</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NP_NULL_PARAM_DEREF_ALL_TARGETS_DANGEROUS">NP: Method call passes null for nonnull parameter</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NP_NULL_PARAM_DEREF_NONVIRTUAL">NP: Non-virtual method call passes null for nonnull parameter</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NP_STORE_INTO_NONNULL_FIELD">NP: Store of null value into field annotated NonNull</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NP_UNWRITTEN_FIELD">NP: Read of unwritten field</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NM_BAD_EQUAL">Nm: Class defines equal(Object); should it be equals(Object)?</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NM_LCASE_HASHCODE">Nm: Class defines hashcode(); should it be hashCode()?</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NM_LCASE_TOSTRING">Nm: Class defines tostring(); should it be toString()?</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NM_METHOD_CONSTRUCTOR_CONFUSION">Nm: Apparent method/constructor confusion</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NM_VERY_CONFUSING">Nm: Very confusing method names</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NM_WRONG_PACKAGE">Nm: Method doesn't override method in superclass due to wrong package for parameter</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#QBA_QUESTIONABLE_BOOLEAN_ASSIGNMENT">QBA: Method assigns boolean literal in boolean expression</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#RC_REF_COMPARISON">RC: Suspicious reference comparison</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#RCN_REDUNDANT_NULLCHECK_WOULD_HAVE_BEEN_A_NPE">RCN: Nullcheck of value previously dereferenced</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#RE_BAD_SYNTAX_FOR_REGULAR_EXPRESSION">RE: Invalid syntax for regular expression</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#RE_CANT_USE_FILE_SEPARATOR_AS_REGULAR_EXPRESSION">RE: File.separator used for regular expression</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#RE_POSSIBLE_UNINTENDED_PATTERN">RE: "." used for regular expression</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#RV_01_TO_INT">RV: Random value from 0 to 1 is coerced to the integer 0</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#RV_ABSOLUTE_VALUE_OF_HASHCODE">RV: Bad attempt to compute absolute value of signed 32-bit hashcode </a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#RV_ABSOLUTE_VALUE_OF_RANDOM_INT">RV: Bad attempt to compute absolute value of signed random integer</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#RV_CHECK_COMPARETO_FOR_SPECIFIC_RETURN_VALUE">RV: Code checks for specific values returned by compareTo</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#RV_EXCEPTION_NOT_THROWN">RV: Exception created and dropped rather than thrown</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#RV_RETURN_VALUE_IGNORED">RV: Method ignores return value</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#RpC_REPEATED_CONDITIONAL_TEST">RpC: Repeated conditional tests</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#SA_FIELD_SELF_ASSIGNMENT">SA: Self assignment of field</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SA_FIELD_SELF_COMPARISON">SA: Self comparison of field with itself</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#SA_FIELD_SELF_COMPUTATION">SA: Nonsensical self computation involving a field (e.g., x & x)</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SA_LOCAL_SELF_ASSIGNMENT_INSTEAD_OF_FIELD">SA: Self assignment of local rather than assignment to field</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#SA_LOCAL_SELF_COMPARISON">SA: Self comparison of value with itself</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SA_LOCAL_SELF_COMPUTATION">SA: Nonsensical self computation involving a variable (e.g., x & x)</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#SF_DEAD_STORE_DUE_TO_SWITCH_FALLTHROUGH">SF: Dead store due to switch statement fall through</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SF_DEAD_STORE_DUE_TO_SWITCH_FALLTHROUGH_TO_THROW">SF: Dead store due to switch statement fall through to throw</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#SIC_THREADLOCAL_DEADLY_EMBRACE">SIC: Deadly embrace of non-static inner class and thread local</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SIO_SUPERFLUOUS_INSTANCEOF">SIO: Unnecessary type check done using instanceof operator</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#SQL_BAD_PREPARED_STATEMENT_ACCESS">SQL: Method attempts to access a prepared statement parameter with index 0</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SQL_BAD_RESULTSET_ACCESS">SQL: Method attempts to access a result set field with index 0</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#STI_INTERRUPTED_ON_CURRENTTHREAD">STI: Unneeded use of currentThread() call, to call interrupted() </a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#STI_INTERRUPTED_ON_UNKNOWNTHREAD">STI: Static Thread.interrupted() method invoked on thread instance</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#SE_METHOD_MUST_BE_PRIVATE">Se: Method must be private in order for serialization to work</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SE_READ_RESOLVE_IS_STATIC">Se: The readResolve method must not be declared as a static method.  </a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#TQ_ALWAYS_VALUE_USED_WHERE_NEVER_REQUIRED">TQ: Value annotated as carrying a type qualifier used where a value that must not carry that qualifier is required</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#TQ_COMPARING_VALUES_WITH_INCOMPATIBLE_TYPE_QUALIFIERS">TQ: Comparing values with incompatible type qualifiers</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#TQ_MAYBE_SOURCE_VALUE_REACHES_ALWAYS_SINK">TQ: Value that might not carry a type qualifier is always used in a way requires that type qualifier</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#TQ_MAYBE_SOURCE_VALUE_REACHES_NEVER_SINK">TQ: Value that might carry a type qualifier is always used in a way prohibits it from having that type qualifier</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#TQ_NEVER_VALUE_USED_WHERE_ALWAYS_REQUIRED">TQ: Value annotated as never carrying a type qualifier used where value carrying that qualifier is required</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#UMAC_UNCALLABLE_METHOD_OF_ANONYMOUS_CLASS">UMAC: Uncallable method defined in anonymous class</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#UR_UNINIT_READ">UR: Uninitialized read of field in constructor</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#UR_UNINIT_READ_CALLED_FROM_SUPER_CONSTRUCTOR">UR: Uninitialized read of field method called from constructor of superclass</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DMI_INVOKING_TOSTRING_ON_ANONYMOUS_ARRAY">USELESS_STRING: Invocation of toString on an array</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DMI_INVOKING_TOSTRING_ON_ARRAY">USELESS_STRING: Invocation of toString on an array</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#VA_FORMAT_STRING_BAD_CONVERSION_FROM_ARRAY">USELESS_STRING: Array formatted in useless way using format string</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#UWF_NULL_FIELD">UwF: Field only ever set to null</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#UWF_UNWRITTEN_FIELD">UwF: Unwritten field</a></td><td>Correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#VA_PRIMITIVE_ARRAY_PASSED_TO_OBJECT_VARARG">VA: Primitive array passed to function expecting a variable number of object arguments</a></td><td>Correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#LG_LOST_LOGGER_DUE_TO_WEAK_REFERENCE">LG: Potential lost logger changes due to weak reference in OpenJDK</a></td><td>Experimental</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#OBL_UNSATISFIED_OBLIGATION">OBL: Method may fail to clean up stream or resource</a></td><td>Experimental</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#OBL_UNSATISFIED_OBLIGATION_EXCEPTION_EDGE">OBL: Method may fail to clean up stream or resource on checked exception</a></td><td>Experimental</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DM_CONVERT_CASE">Dm: Consider using Locale parameterized version of invoked method</a></td><td>Internationalization</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DM_DEFAULT_ENCODING">Dm: Reliance on default encoding</a></td><td>Internationalization</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DP_CREATE_CLASSLOADER_INSIDE_DO_PRIVILEGED">DP: Classloaders should only be created inside doPrivileged block</a></td><td>Malicious code vulnerability</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DP_DO_INSIDE_DO_PRIVILEGED">DP: Method invoked that should be only be invoked inside a doPrivileged block</a></td><td>Malicious code vulnerability</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#EI_EXPOSE_REP">EI: May expose internal representation by returning reference to mutable object</a></td><td>Malicious code vulnerability</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#EI_EXPOSE_REP2">EI2: May expose internal representation by incorporating reference to mutable object</a></td><td>Malicious code vulnerability</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#FI_PUBLIC_SHOULD_BE_PROTECTED">FI: Finalizer should be protected, not public</a></td><td>Malicious code vulnerability</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#EI_EXPOSE_STATIC_REP2">MS: May expose internal static state by storing a mutable object into a static field</a></td><td>Malicious code vulnerability</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#MS_CANNOT_BE_FINAL">MS: Field isn't final and can't be protected from malicious code</a></td><td>Malicious code vulnerability</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#MS_EXPOSE_REP">MS: Public static method may expose internal representation by returning array</a></td><td>Malicious code vulnerability</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#MS_FINAL_PKGPROTECT">MS: Field should be both final and package protected</a></td><td>Malicious code vulnerability</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#MS_MUTABLE_ARRAY">MS: Field is a mutable array</a></td><td>Malicious code vulnerability</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#MS_MUTABLE_HASHTABLE">MS: Field is a mutable Hashtable</a></td><td>Malicious code vulnerability</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#MS_OOI_PKGPROTECT">MS: Field should be moved out of an interface and made package protected</a></td><td>Malicious code vulnerability</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#MS_PKGPROTECT">MS: Field should be package protected</a></td><td>Malicious code vulnerability</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#MS_SHOULD_BE_FINAL">MS: Field isn't final but should be</a></td><td>Malicious code vulnerability</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#MS_SHOULD_BE_REFACTORED_TO_BE_FINAL">MS: Field isn't final but should be refactored to be so</a></td><td>Malicious code vulnerability</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#AT_OPERATION_SEQUENCE_ON_CONCURRENT_ABSTRACTION">AT: Sequence of calls to concurrent abstraction may not be atomic</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DC_DOUBLECHECK">DC: Possible double check of field</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DL_SYNCHRONIZATION_ON_BOOLEAN">DL: Synchronization on Boolean</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DL_SYNCHRONIZATION_ON_BOXED_PRIMITIVE">DL: Synchronization on boxed primitive</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DL_SYNCHRONIZATION_ON_SHARED_CONSTANT">DL: Synchronization on interned String </a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DL_SYNCHRONIZATION_ON_UNSHARED_BOXED_PRIMITIVE">DL: Synchronization on boxed primitive values</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DM_MONITOR_WAIT_ON_CONDITION">Dm: Monitor wait() called on Condition</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DM_USELESS_THREAD">Dm: A thread was created using the default empty run method</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#ESync_EMPTY_SYNC">ESync: Empty synchronized block</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#IS2_INCONSISTENT_SYNC">IS: Inconsistent synchronization</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#IS_FIELD_NOT_GUARDED">IS: Field not guarded against concurrent access</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#JLM_JSR166_LOCK_MONITORENTER">JLM: Synchronization performed on Lock</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#JLM_JSR166_UTILCONCURRENT_MONITORENTER">JLM: Synchronization performed on util.concurrent instance</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#JML_JSR166_CALLING_WAIT_RATHER_THAN_AWAIT">JLM: Using monitor style wait methods on util.concurrent abstraction</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#LI_LAZY_INIT_STATIC">LI: Incorrect lazy initialization of static field</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#LI_LAZY_INIT_UPDATE_STATIC">LI: Incorrect lazy initialization and update of static field</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#ML_SYNC_ON_FIELD_TO_GUARD_CHANGING_THAT_FIELD">ML: Synchronization on field in futile attempt to guard that field</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#ML_SYNC_ON_UPDATED_FIELD">ML: Method synchronizes on an updated field</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#MSF_MUTABLE_SERVLET_FIELD">MSF: Mutable servlet field</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#MWN_MISMATCHED_NOTIFY">MWN: Mismatched notify()</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#MWN_MISMATCHED_WAIT">MWN: Mismatched wait()</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NN_NAKED_NOTIFY">NN: Naked notify</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NP_SYNC_AND_NULL_CHECK_FIELD">NP: Synchronize and null check on the same field.</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NO_NOTIFY_NOT_NOTIFYALL">No: Using notify() rather than notifyAll()</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#RS_READOBJECT_SYNC">RS: Class's readObject() method is synchronized</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#RV_RETURN_VALUE_OF_PUTIFABSENT_IGNORED">RV: Return value of putIfAbsent ignored, value passed to putIfAbsent reused</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#RU_INVOKE_RUN">Ru: Invokes run on a thread (did you mean to start it instead?)</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SC_START_IN_CTOR">SC: Constructor invokes Thread.start()</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#SP_SPIN_ON_FIELD">SP: Method spins on field</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#STCAL_INVOKE_ON_STATIC_CALENDAR_INSTANCE">STCAL: Call to static Calendar</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#STCAL_INVOKE_ON_STATIC_DATE_FORMAT_INSTANCE">STCAL: Call to static DateFormat</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#STCAL_STATIC_CALENDAR_INSTANCE">STCAL: Static Calendar field</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#STCAL_STATIC_SIMPLE_DATE_FORMAT_INSTANCE">STCAL: Static DateFormat</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SWL_SLEEP_WITH_LOCK_HELD">SWL: Method calls Thread.sleep() with a lock held</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#TLW_TWO_LOCK_WAIT">TLW: Wait with two locks held</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#UG_SYNC_SET_UNSYNC_GET">UG: Unsynchronized get method, synchronized set method</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#UL_UNRELEASED_LOCK">UL: Method does not release lock on all paths</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#UL_UNRELEASED_LOCK_EXCEPTION_PATH">UL: Method does not release lock on all exception paths</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#UW_UNCOND_WAIT">UW: Unconditional wait</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#VO_VOLATILE_INCREMENT">VO: An increment to a volatile field isn't atomic</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#VO_VOLATILE_REFERENCE_TO_ARRAY">VO: A volatile reference to an array doesn't treat the array elements as volatile</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#WL_USING_GETCLASS_RATHER_THAN_CLASS_LITERAL">WL: Synchronization on getClass rather than class literal</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#WS_WRITEOBJECT_SYNC">WS: Class's writeObject() method is synchronized but nothing else is</a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#WA_AWAIT_NOT_IN_LOOP">Wa: Condition.await() not in loop </a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#WA_NOT_IN_LOOP">Wa: Wait not in loop </a></td><td>Multithreaded correctness</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#BX_BOXING_IMMEDIATELY_UNBOXED">Bx: Primitive value is boxed and then immediately unboxed</a></td><td>Performance</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#BX_BOXING_IMMEDIATELY_UNBOXED_TO_PERFORM_COERCION">Bx: Primitive value is boxed then unboxed to perform primitive coercion</a></td><td>Performance</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#BX_UNBOXING_IMMEDIATELY_REBOXED">Bx: Boxed value is unboxed and then immediately reboxed</a></td><td>Performance</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DM_BOXED_PRIMITIVE_TOSTRING">Bx: Method allocates a boxed primitive just to call toString</a></td><td>Performance</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DM_FP_NUMBER_CTOR">Bx: Method invokes inefficient floating-point Number constructor; use static valueOf instead</a></td><td>Performance</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DM_NUMBER_CTOR">Bx: Method invokes inefficient Number constructor; use static valueOf instead</a></td><td>Performance</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DMI_BLOCKING_METHODS_ON_URL">Dm: The equals and hashCode methods of URL are blocking</a></td><td>Performance</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DMI_COLLECTION_OF_URLS">Dm: Maps and sets of URLs can be performance hogs</a></td><td>Performance</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DM_BOOLEAN_CTOR">Dm: Method invokes inefficient Boolean constructor; use Boolean.valueOf(...) instead</a></td><td>Performance</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DM_GC">Dm: Explicit garbage collection; extremely dubious except in benchmarking code</a></td><td>Performance</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DM_NEW_FOR_GETCLASS">Dm: Method allocates an object, only to get the class object</a></td><td>Performance</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DM_NEXTINT_VIA_NEXTDOUBLE">Dm: Use the nextInt method of Random rather than nextDouble to generate a random integer</a></td><td>Performance</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DM_STRING_CTOR">Dm: Method invokes inefficient new String(String) constructor</a></td><td>Performance</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DM_STRING_TOSTRING">Dm: Method invokes toString() method on a String</a></td><td>Performance</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DM_STRING_VOID_CTOR">Dm: Method invokes inefficient new String() constructor</a></td><td>Performance</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#HSC_HUGE_SHARED_STRING_CONSTANT">HSC: Huge string constants is duplicated across multiple class files</a></td><td>Performance</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#ITA_INEFFICIENT_TO_ARRAY">ITA: Method uses toArray() with zero-length array argument</a></td><td>Performance</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#SBSC_USE_STRINGBUFFER_CONCATENATION">SBSC: Method concatenates strings using + in a loop</a></td><td>Performance</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SIC_INNER_SHOULD_BE_STATIC">SIC: Should be a static inner class</a></td><td>Performance</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#SIC_INNER_SHOULD_BE_STATIC_ANON">SIC: Could be refactored into a named static inner class</a></td><td>Performance</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SIC_INNER_SHOULD_BE_STATIC_NEEDS_THIS">SIC: Could be refactored into a static inner class</a></td><td>Performance</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#SS_SHOULD_BE_STATIC">SS: Unread field: should this field be static?</a></td><td>Performance</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#UM_UNNECESSARY_MATH">UM: Method calls static Math class method on a constant value</a></td><td>Performance</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#UPM_UNCALLED_PRIVATE_METHOD">UPM: Private method is never called</a></td><td>Performance</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#URF_UNREAD_FIELD">UrF: Unread field</a></td><td>Performance</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#UUF_UNUSED_FIELD">UuF: Unused field</a></td><td>Performance</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#WMI_WRONG_MAP_ITERATOR">WMI: Inefficient use of keySet iterator instead of entrySet iterator</a></td><td>Performance</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DMI_CONSTANT_DB_PASSWORD">Dm: Hardcoded constant database password</a></td><td>Security</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DMI_EMPTY_DB_PASSWORD">Dm: Empty database password</a></td><td>Security</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#HRS_REQUEST_PARAMETER_TO_COOKIE">HRS: HTTP cookie formed from untrusted input</a></td><td>Security</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#HRS_REQUEST_PARAMETER_TO_HTTP_HEADER">HRS: HTTP Response splitting vulnerability</a></td><td>Security</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#PT_ABSOLUTE_PATH_TRAVERSAL">PT: Absolute path traversal in servlet</a></td><td>Security</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#PT_RELATIVE_PATH_TRAVERSAL">PT: Relative path traversal in servlet</a></td><td>Security</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#SQL_NONCONSTANT_STRING_PASSED_TO_EXECUTE">SQL: Nonconstant string passed to execute method on an SQL statement</a></td><td>Security</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SQL_PREPARED_STATEMENT_GENERATED_FROM_NONCONSTANT_STRING">SQL: A prepared statement is generated from a nonconstant String</a></td><td>Security</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#XSS_REQUEST_PARAMETER_TO_JSP_WRITER">XSS: JSP reflected cross site scripting vulnerability</a></td><td>Security</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#XSS_REQUEST_PARAMETER_TO_SEND_ERROR">XSS: Servlet reflected cross site scripting vulnerability in error page</a></td><td>Security</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#XSS_REQUEST_PARAMETER_TO_SERVLET_WRITER">XSS: Servlet reflected cross site scripting vulnerability</a></td><td>Security</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#BC_BAD_CAST_TO_ABSTRACT_COLLECTION">BC: Questionable cast to abstract collection </a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#BC_BAD_CAST_TO_CONCRETE_COLLECTION">BC: Questionable cast to concrete collection</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#BC_UNCONFIRMED_CAST">BC: Unchecked/unconfirmed cast</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#BC_UNCONFIRMED_CAST_OF_RETURN_VALUE">BC: Unchecked/unconfirmed cast of return value from method</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#BC_VACUOUS_INSTANCEOF">BC: instanceof will always return true</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#ICAST_QUESTIONABLE_UNSIGNED_RIGHT_SHIFT">BSHIFT: Unsigned right shift cast to short/byte</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#CI_CONFUSED_INHERITANCE">CI: Class is final but declares protected field</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DB_DUPLICATE_BRANCHES">DB: Method uses the same code for two branches</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DB_DUPLICATE_SWITCH_CLAUSES">DB: Method uses the same code for two switch clauses</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DLS_DEAD_LOCAL_STORE">DLS: Dead store to local variable</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DLS_DEAD_LOCAL_STORE_IN_RETURN">DLS: Useless assignment in return statement</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DLS_DEAD_LOCAL_STORE_OF_NULL">DLS: Dead store of null to local variable</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DLS_DEAD_LOCAL_STORE_SHADOWS_FIELD">DLS: Dead store to local variable that shadows field</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DMI_HARDCODED_ABSOLUTE_FILENAME">DMI: Code contains a hard coded reference to an absolute pathname</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DMI_NONSERIALIZABLE_OBJECT_WRITTEN">DMI: Non serializable object written to ObjectOutput</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#DMI_USELESS_SUBSTRING">DMI: Invocation of substring(0), which returns the original value</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#DMI_THREAD_PASSED_WHERE_RUNNABLE_EXPECTED">Dm: Thread passed where Runnable expected</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#EQ_DOESNT_OVERRIDE_EQUALS">Eq: Class doesn't override equals in superclass</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#EQ_UNUSUAL">Eq: Unusual equals method </a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#FE_FLOATING_POINT_EQUALITY">FE: Test for floating point equality</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#VA_FORMAT_STRING_BAD_CONVERSION_TO_BOOLEAN">FS: Non-Boolean argument formatted using %b format specifier</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#IA_AMBIGUOUS_INVOCATION_OF_INHERITED_OR_OUTER_METHOD">IA: Ambiguous invocation of either an inherited or outer method</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#IC_INIT_CIRCULARITY">IC: Initialization circularity</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#ICAST_IDIV_CAST_TO_DOUBLE">ICAST: integral division result cast to double or float</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#ICAST_INTEGER_MULTIPLY_CAST_TO_LONG">ICAST: Result of integer multiplication cast to long</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#IM_AVERAGE_COMPUTATION_COULD_OVERFLOW">IM: Computation of average could overflow</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#IM_BAD_CHECK_FOR_ODD">IM: Check for oddness that won't work for negative numbers </a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#INT_BAD_REM_BY_1">INT: Integer remainder modulo 1</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#INT_VACUOUS_BIT_OPERATION">INT: Vacuous bit mask operation on integer value</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#INT_VACUOUS_COMPARISON">INT: Vacuous comparison of integer value</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#MTIA_SUSPECT_SERVLET_INSTANCE_FIELD">MTIA: Class extends Servlet class and uses instance variables</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#MTIA_SUSPECT_STRUTS_INSTANCE_FIELD">MTIA: Class extends Struts Action class and uses instance variables</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NP_DEREFERENCE_OF_READLINE_VALUE">NP: Dereference of the result of readLine() without nullcheck</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NP_IMMEDIATE_DEREFERENCE_OF_READLINE">NP: Immediate dereference of the result of readLine()</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NP_LOAD_OF_KNOWN_NULL_VALUE">NP: Load of known null value</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NP_NULL_ON_SOME_PATH_FROM_RETURN_VALUE">NP: Possible null pointer dereference due to return value of called method</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NP_NULL_ON_SOME_PATH_MIGHT_BE_INFEASIBLE">NP: Possible null pointer dereference on branch that might be infeasible</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NP_PARAMETER_MUST_BE_NONNULL_BUT_MARKED_AS_NULLABLE">NP: Parameter must be nonnull but is marked as nullable</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NP_UNWRITTEN_PUBLIC_OR_PROTECTED_FIELD">NP: Read of unwritten public or protected field</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#NS_DANGEROUS_NON_SHORT_CIRCUIT">NS: Potentially dangerous use of non-short-circuit logic</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#NS_NON_SHORT_CIRCUIT">NS: Questionable use of non-short-circuit logic</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#PZLA_PREFER_ZERO_LENGTH_ARRAYS">PZLA: Consider returning a zero length array rather than null</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#QF_QUESTIONABLE_FOR_LOOP">QF: Complicated, subtle or wrong increment in for-loop </a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#RCN_REDUNDANT_COMPARISON_OF_NULL_AND_NONNULL_VALUE">RCN: Redundant comparison of non-null value to null</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#RCN_REDUNDANT_COMPARISON_TWO_NULL_VALUES">RCN: Redundant comparison of two null values</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#RCN_REDUNDANT_NULLCHECK_OF_NONNULL_VALUE">RCN: Redundant nullcheck of value known to be non-null</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#RCN_REDUNDANT_NULLCHECK_OF_NULL_VALUE">RCN: Redundant nullcheck of value known to be null</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#REC_CATCH_EXCEPTION">REC: Exception is caught when Exception is not thrown</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#RI_REDUNDANT_INTERFACES">RI: Class implements same interface as superclass</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#RV_CHECK_FOR_POSITIVE_INDEXOF">RV: Method checks to see if result of String.indexOf is positive</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#RV_DONT_JUST_NULL_CHECK_READLINE">RV: Method discards result of readLine after checking if it is nonnull</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#RV_REM_OF_HASHCODE">RV: Remainder of hashCode could be negative</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#RV_REM_OF_RANDOM_INT">RV: Remainder of 32-bit signed random integer</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#RV_RETURN_VALUE_IGNORED_INFERRED">RV: Method ignores return value, is this OK?</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SA_FIELD_DOUBLE_ASSIGNMENT">SA: Double assignment of field</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#SA_LOCAL_DOUBLE_ASSIGNMENT">SA: Double assignment of local variable </a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SA_LOCAL_SELF_ASSIGNMENT">SA: Self assignment of local variable</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#SF_SWITCH_FALLTHROUGH">SF: Switch statement found where one case falls through to the next case</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SF_SWITCH_NO_DEFAULT">SF: Switch statement found where default case is missing</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#ST_WRITE_TO_STATIC_FROM_INSTANCE_METHOD">ST: Write to static field from instance method</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#SE_PRIVATE_READ_RESOLVE_NOT_INHERITED">Se: private readResolve method not inherited by subclasses</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#SE_TRANSIENT_FIELD_OF_NONSERIALIZABLE_CLASS">Se: Transient field of class that isn't Serializable. </a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#TQ_EXPLICIT_UNKNOWN_SOURCE_VALUE_REACHES_ALWAYS_SINK">TQ: Value required to have type qualifier, but marked as unknown</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#TQ_EXPLICIT_UNKNOWN_SOURCE_VALUE_REACHES_NEVER_SINK">TQ: Value required to not have type qualifier, but marked as unknown</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#UCF_USELESS_CONTROL_FLOW">UCF: Useless control flow</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#UCF_USELESS_CONTROL_FLOW_NEXT_LINE">UCF: Useless control flow to next line</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#URF_UNREAD_PUBLIC_OR_PROTECTED_FIELD">UrF: Unread public/protected field</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#UUF_UNUSED_PUBLIC_OR_PROTECTED_FIELD">UuF: Unused public or protected field</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#UWF_FIELD_NOT_INITIALIZED_IN_CONSTRUCTOR">UwF: Field not initialized in constructor but dereferenced without null check</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#UWF_UNWRITTEN_PUBLIC_OR_PROTECTED_FIELD">UwF: Unwritten public or protected field</a></td><td>Dodgy code</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#XFB_XML_FACTORY_BYPASS">XFB: Method directly allocates a specific implementation of xml interfaces</a></td><td>Dodgy code</td></tr>
+</table>
+<h2>Descriptions</h2>
+<h3><a name="AM_CREATES_EMPTY_JAR_FILE_ENTRY">AM: Creates an empty jar file entry (AM_CREATES_EMPTY_JAR_FILE_ENTRY)</a></h3>
+
+
+<p>The code calls <code>putNextEntry()</code>, immediately
+followed by a call to <code>closeEntry()</code>. This results
+in an empty JarFile entry. The contents of the entry
+should be written to the JarFile between the calls to
+<code>putNextEntry()</code> and
+<code>closeEntry()</code>.</p>
+
+    
+<h3><a name="AM_CREATES_EMPTY_ZIP_FILE_ENTRY">AM: Creates an empty zip file entry (AM_CREATES_EMPTY_ZIP_FILE_ENTRY)</a></h3>
+
+
+<p>The code calls <code>putNextEntry()</code>, immediately
+followed by a call to <code>closeEntry()</code>. This results
+in an empty ZipFile entry. The contents of the entry
+should be written to the ZipFile between the calls to
+<code>putNextEntry()</code> and
+<code>closeEntry()</code>.</p>
+
+    
+<h3><a name="BC_EQUALS_METHOD_SHOULD_WORK_FOR_ALL_OBJECTS">BC: Equals method should not assume anything about the type of its argument (BC_EQUALS_METHOD_SHOULD_WORK_FOR_ALL_OBJECTS)</a></h3>
+
+
+<p>
+The <code>equals(Object o)</code> method shouldn't make any assumptions
+about the type of <code>o</code>. It should simply return
+false if <code>o</code> is not the same type as <code>this</code>.
+</p>
+
+    
+<h3><a name="BIT_SIGNED_CHECK">BIT: Check for sign of bitwise operation (BIT_SIGNED_CHECK)</a></h3>
+
+
+<p> This method compares an expression such as
+<pre>((event.detail &amp; SWT.SELECTED) &gt; 0)</pre>.
+Using bit arithmetic and then comparing with the greater than operator can
+lead to unexpected results (of course depending on the value of
+SWT.SELECTED). If SWT.SELECTED is a negative number, this is a candidate
+for a bug. Even when SWT.SELECTED is not negative, it seems good practice
+to use '!= 0' instead of '&gt; 0'.
+</p>
+<p>
+<em>Boris Bokowski</em>
+</p>
+
+    
+<h3><a name="CN_IDIOM">CN: Class implements Cloneable but does not define or use clone method (CN_IDIOM)</a></h3>
+
+
+<p>
+   Class implements Cloneable but does not define or
+   use the clone method.</p>
+
+    
+<h3><a name="CN_IDIOM_NO_SUPER_CALL">CN: clone method does not call super.clone() (CN_IDIOM_NO_SUPER_CALL)</a></h3>
+
+
+<p> This non-final class defines a clone() method that does not call super.clone().
+If this class ("<i>A</i>") is extended by a subclass ("<i>B</i>"),
+and the subclass <i>B</i> calls super.clone(), then it is likely that
+<i>B</i>'s clone() method will return an object of type <i>A</i>,
+which violates the standard contract for clone().</p>
+
+<p> If all clone() methods call super.clone(), then they are guaranteed
+to use Object.clone(), which always returns an object of the correct type.</p>
+
+    
+<h3><a name="CN_IMPLEMENTS_CLONE_BUT_NOT_CLONEABLE">CN: Class defines clone() but doesn't implement Cloneable (CN_IMPLEMENTS_CLONE_BUT_NOT_CLONEABLE)</a></h3>
+
+
+<p> This class defines a clone() method but the class doesn't implement Cloneable.
+There are some situations in which this is OK (e.g., you want to control how subclasses
+can clone themselves), but just make sure that this is what you intended.
+</p>
+
+    
+<h3><a name="CO_ABSTRACT_SELF">Co: Abstract class defines covariant compareTo() method (CO_ABSTRACT_SELF)</a></h3>
+
+
+  <p> This class defines a covariant version of <code>compareTo()</code>.&nbsp;
+  To correctly override the <code>compareTo()</code> method in the
+  <code>Comparable</code> interface, the parameter of <code>compareTo()</code>
+  must have type <code>java.lang.Object</code>.</p>
+
+    
+<h3><a name="CO_SELF_NO_OBJECT">Co: Covariant compareTo() method defined (CO_SELF_NO_OBJECT)</a></h3>
+
+
+  <p> This class defines a covariant version of <code>compareTo()</code>.&nbsp;
+  To correctly override the <code>compareTo()</code> method in the
+  <code>Comparable</code> interface, the parameter of <code>compareTo()</code>
+  must have type <code>java.lang.Object</code>.</p>
+
+    
+<h3><a name="DE_MIGHT_DROP">DE: Method might drop exception (DE_MIGHT_DROP)</a></h3>
+
+
+  <p> This method might drop an exception.&nbsp; In general, exceptions
+  should be handled or reported in some way, or they should be thrown
+  out of the method.</p>
+
+    
+<h3><a name="DE_MIGHT_IGNORE">DE: Method might ignore exception (DE_MIGHT_IGNORE)</a></h3>
+
+
+  <p> This method might ignore an exception.&nbsp; In general, exceptions
+  should be handled or reported in some way, or they should be thrown
+  out of the method.</p>
+
+    
+<h3><a name="DMI_ENTRY_SETS_MAY_REUSE_ENTRY_OBJECTS">DMI: Adding elements of an entry set may fail due to reuse of Entry objects (DMI_ENTRY_SETS_MAY_REUSE_ENTRY_OBJECTS)</a></h3>
+
+     
+     <p> The entrySet() method is allowed to return a view of the
+     underlying Map in which a single Entry object is reused and returned
+     during the iteration.  As of Java 1.6, both IdentityHashMap
+     and EnumMap did so. When iterating through such a Map,
+     the Entry value is only valid until you advance to the next iteration.
+     If, for example, you try to pass such an entrySet to an addAll method,
+     things will go badly wrong.
+    </p>
+     
+    
+<h3><a name="DMI_RANDOM_USED_ONLY_ONCE">DMI: Random object created and used only once (DMI_RANDOM_USED_ONLY_ONCE)</a></h3>
+
+
+<p> This code creates a java.util.Random object, uses it to generate one random number, and then discards
+the Random object. This produces mediocre quality random numbers and is inefficient.
+If possible, rewrite the code so that the Random object is created once and saved, and each time a new random number
+is required invoke a method on the existing Random object to obtain it.
+</p>
+
+<p>If it is important that the generated Random numbers not be guessable, you <em>must</em> not create a new Random for each random
+number; the values are too easily guessable. You should strongly consider using a java.security.SecureRandom instead
+(and avoid allocating a new SecureRandom for each random number needed).
+</p>
+
+    
+<h3><a name="DMI_USING_REMOVEALL_TO_CLEAR_COLLECTION">DMI: Don't use removeAll to clear a collection (DMI_USING_REMOVEALL_TO_CLEAR_COLLECTION)</a></h3>
+
+     
+     <p> If you want to remove all elements from a collection <code>c</code>, use <code>c.clear</code>,
+not <code>c.removeAll(c)</code>. Calling  <code>c.removeAll(c)</code> to clear a collection
+is less clear, susceptible to errors from typos, less efficient and
+for some collections, might throw a <code>ConcurrentModificationException</code>.
+    </p>
+     
+    
+<h3><a name="DM_EXIT">Dm: Method invokes System.exit(...) (DM_EXIT)</a></h3>
+
+
+  <p> Invoking System.exit shuts down the entire Java virtual machine. This
+   should only been done when it is appropriate. Such calls make it
+   hard or impossible for your code to be invoked by other code.
+   Consider throwing a RuntimeException instead.</p>
+
+    
+<h3><a name="DM_RUN_FINALIZERS_ON_EXIT">Dm: Method invokes dangerous method runFinalizersOnExit (DM_RUN_FINALIZERS_ON_EXIT)</a></h3>
+
+
+  <p> <em>Never call System.runFinalizersOnExit
+or Runtime.runFinalizersOnExit for any reason: they are among the most
+dangerous methods in the Java libraries.</em> -- Joshua Bloch</p>
+
+    
+<h3><a name="ES_COMPARING_PARAMETER_STRING_WITH_EQ">ES: Comparison of String parameter using == or != (ES_COMPARING_PARAMETER_STRING_WITH_EQ)</a></h3>
+
+
+  <p>This code compares a <code>java.lang.String</code> parameter for reference
+equality using the == or != operators. Requiring callers to
+pass only String constants or interned strings to a method is unnecessarily
+fragile, and rarely leads to measurable performance gains. Consider
+using the <code>equals(Object)</code> method instead.</p>
+
+    
+<h3><a name="ES_COMPARING_STRINGS_WITH_EQ">ES: Comparison of String objects using == or != (ES_COMPARING_STRINGS_WITH_EQ)</a></h3>
+
+
+  <p>This code compares <code>java.lang.String</code> objects for reference
+equality using the == or != operators.
+Unless both strings are either constants in a source file, or have been
+interned using the <code>String.intern()</code> method, the same string
+value may be represented by two different String objects. Consider
+using the <code>equals(Object)</code> method instead.</p>
+
+    
+<h3><a name="EQ_ABSTRACT_SELF">Eq: Abstract class defines covariant equals() method (EQ_ABSTRACT_SELF)</a></h3>
+
+
+  <p> This class defines a covariant version of <code>equals()</code>.&nbsp;
+  To correctly override the <code>equals()</code> method in
+  <code>java.lang.Object</code>, the parameter of <code>equals()</code>
+  must have type <code>java.lang.Object</code>.</p>
+
+    
+<h3><a name="EQ_CHECK_FOR_OPERAND_NOT_COMPATIBLE_WITH_THIS">Eq: Equals checks for incompatible operand (EQ_CHECK_FOR_OPERAND_NOT_COMPATIBLE_WITH_THIS)</a></h3>
+
+
+  <p> This equals method is checking to see if the argument is some incompatible type
+(i.e., a class that is neither a supertype nor subtype of the class that defines
+the equals method). For example, the Foo class might have an equals method
+that looks like:
+
+<p><code><pre>
+public boolean equals(Object o) {
+  if (o instanceof Foo)
+    return name.equals(((Foo)o).name);
+  else if (o instanceof String)
+    return name.equals(o);
+  else return false;
+</pre></code></p>
+
+<p>This is considered bad practice, as it makes it very hard to implement an equals method that
+is symmetric and transitive. Without those properties, very unexpected behavoirs are possible.
+</p>
+
+    
+<h3><a name="EQ_COMPARETO_USE_OBJECT_EQUALS">Eq: Class defines compareTo(...) and uses Object.equals() (EQ_COMPARETO_USE_OBJECT_EQUALS)</a></h3>
+
+
+  <p> This class defines a <code>compareTo(...)</code> method but inherits its
+  <code>equals()</code> method from <code>java.lang.Object</code>.
+    Generally, the value of compareTo should return zero if and only if
+    equals returns true. If this is violated, weird and unpredictable
+    failures will occur in classes such as PriorityQueue.
+    In Java 5 the PriorityQueue.remove method uses the compareTo method,
+    while in Java 6 it uses the equals method.
+
+<p>From the JavaDoc for the compareTo method in the Comparable interface:
+<blockquote>
+It is strongly recommended, but not strictly required that <code>(x.compareTo(y)==0) == (x.equals(y))</code>.
+Generally speaking, any class that implements the Comparable interface and violates this condition
+should clearly indicate this fact. The recommended language
+is "Note: this class has a natural ordering that is inconsistent with equals."
+</blockquote>
+
+    
+<h3><a name="EQ_GETCLASS_AND_CLASS_CONSTANT">Eq: equals method fails for subtypes (EQ_GETCLASS_AND_CLASS_CONSTANT)</a></h3>
+
+
+  <p> This class has an equals method that will be broken if it is inherited by subclasses.
+It compares a class literal with the class of the argument (e.g., in class <code>Foo</code>
+it might check if <code>Foo.class == o.getClass()</code>).
+It is better to check if <code>this.getClass() == o.getClass()</code>.
+</p>
+
+    
+<h3><a name="EQ_SELF_NO_OBJECT">Eq: Covariant equals() method defined (EQ_SELF_NO_OBJECT)</a></h3>
+
+
+  <p> This class defines a covariant version of <code>equals()</code>.&nbsp;
+  To correctly override the <code>equals()</code> method in
+  <code>java.lang.Object</code>, the parameter of <code>equals()</code>
+  must have type <code>java.lang.Object</code>.</p>
+
+    
+<h3><a name="FI_EMPTY">FI: Empty finalizer should be deleted (FI_EMPTY)</a></h3>
+
+
+  <p> Empty <code>finalize()</code> methods are useless, so they should
+  be deleted.</p>
+
+    
+<h3><a name="FI_EXPLICIT_INVOCATION">FI: Explicit invocation of finalizer (FI_EXPLICIT_INVOCATION)</a></h3>
+
+
+  <p> This method contains an explicit invocation of the <code>finalize()</code>
+  method on an object.&nbsp; Because finalizer methods are supposed to be
+  executed once, and only by the VM, this is a bad idea.</p>
+<p>If a connected set of objects beings finalizable, then the VM will invoke the
+finalize method on all the finalizable object, possibly at the same time in different threads.
+Thus, it is a particularly bad idea, in the finalize method for a class X, invoke finalize
+on objects referenced by X, because they may already be getting finalized in a separate thread.
+
+    
+<h3><a name="FI_FINALIZER_NULLS_FIELDS">FI: Finalizer nulls fields (FI_FINALIZER_NULLS_FIELDS)</a></h3>
+
+
+  <p> This finalizer nulls out fields.  This is usually an error, as it does not aid garbage collection,
+  and the object is going to be garbage collected anyway.
+
+    
+<h3><a name="FI_FINALIZER_ONLY_NULLS_FIELDS">FI: Finalizer only nulls fields (FI_FINALIZER_ONLY_NULLS_FIELDS)</a></h3>
+
+
+  <p> This finalizer does nothing except null out fields. This is completely pointless, and requires that
+the object be garbage collected, finalized, and then garbage collected again. You should just remove the finalize
+method.
+
+    
+<h3><a name="FI_MISSING_SUPER_CALL">FI: Finalizer does not call superclass finalizer (FI_MISSING_SUPER_CALL)</a></h3>
+
+
+  <p> This <code>finalize()</code> method does not make a call to its
+  superclass's <code>finalize()</code> method.&nbsp; So, any finalizer
+  actions defined for the superclass will not be performed.&nbsp;
+  Add a call to <code>super.finalize()</code>.</p>
+
+    
+<h3><a name="FI_NULLIFY_SUPER">FI: Finalizer nullifies superclass finalizer (FI_NULLIFY_SUPER)</a></h3>
+
+
+  <p> This empty <code>finalize()</code> method explicitly negates the
+  effect of any finalizer defined by its superclass.&nbsp; Any finalizer
+  actions defined for the superclass will not be performed.&nbsp;
+  Unless this is intended, delete this method.</p>
+
+    
+<h3><a name="FI_USELESS">FI: Finalizer does nothing but call superclass finalizer (FI_USELESS)</a></h3>
+
+
+  <p> The only thing this <code>finalize()</code> method does is call
+  the superclass's <code>finalize()</code> method, making it
+  redundant.&nbsp; Delete it.</p>
+
+    
+<h3><a name="VA_FORMAT_STRING_USES_NEWLINE">FS: Format string should use %n rather than \n (VA_FORMAT_STRING_USES_NEWLINE)</a></h3>
+
+
+<p>
+This format string include a newline character (\n). In format strings, it is generally
+ preferable better to use %n, which will produce the platform-specific line separator.
+</p>
+
+     
+<h3><a name="GC_UNCHECKED_TYPE_IN_GENERIC_CALL">GC: Unchecked type in generic call (GC_UNCHECKED_TYPE_IN_GENERIC_CALL)</a></h3>
+
+     
+     <p> This call to a generic collection method passes an argument
+    while compile type Object where a specific type from
+    the generic type parameters is expected.
+    Thus, neither the standard Java type system nor static analysis
+    can provide useful information on whether the
+    object being passed as a parameter is of an appropriate type.
+    </p>
+     
+    
+<h3><a name="HE_EQUALS_NO_HASHCODE">HE: Class defines equals() but not hashCode() (HE_EQUALS_NO_HASHCODE)</a></h3>
+
+
+  <p> This class overrides <code>equals(Object)</code>, but does not
+  override <code>hashCode()</code>.&nbsp; Therefore, the class may violate the
+  invariant that equal objects must have equal hashcodes.</p>
+
+    
+<h3><a name="HE_EQUALS_USE_HASHCODE">HE: Class defines equals() and uses Object.hashCode() (HE_EQUALS_USE_HASHCODE)</a></h3>
+
+
+  <p> This class overrides <code>equals(Object)</code>, but does not
+  override <code>hashCode()</code>, and inherits the implementation of
+  <code>hashCode()</code> from <code>java.lang.Object</code> (which returns
+  the identity hash code, an arbitrary value assigned to the object
+  by the VM).&nbsp; Therefore, the class is very likely to violate the
+  invariant that equal objects must have equal hashcodes.</p>
+
+<p>If you don't think instances of this class will ever be inserted into a HashMap/HashTable,
+the recommended <code>hashCode</code> implementation to use is:</p>
+<pre>public int hashCode() {
+  assert false : "hashCode not designed";
+  return 42; // any arbitrary constant will do
+  }</pre>
+
+    
+<h3><a name="HE_HASHCODE_NO_EQUALS">HE: Class defines hashCode() but not equals() (HE_HASHCODE_NO_EQUALS)</a></h3>
+
+
+  <p> This class defines a <code>hashCode()</code> method but not an
+  <code>equals()</code> method.&nbsp; Therefore, the class may
+  violate the invariant that equal objects must have equal hashcodes.</p>
+
+    
+<h3><a name="HE_HASHCODE_USE_OBJECT_EQUALS">HE: Class defines hashCode() and uses Object.equals() (HE_HASHCODE_USE_OBJECT_EQUALS)</a></h3>
+
+
+  <p> This class defines a <code>hashCode()</code> method but inherits its
+  <code>equals()</code> method from <code>java.lang.Object</code>
+  (which defines equality by comparing object references).&nbsp; Although
+  this will probably satisfy the contract that equal objects must have
+  equal hashcodes, it is probably not what was intended by overriding
+  the <code>hashCode()</code> method.&nbsp; (Overriding <code>hashCode()</code>
+  implies that the object's identity is based on criteria more complicated
+  than simple reference equality.)</p>
+<p>If you don't think instances of this class will ever be inserted into a HashMap/HashTable,
+the recommended <code>hashCode</code> implementation to use is:</p>
+<p><pre>public int hashCode() {
+  assert false : "hashCode not designed";
+  return 42; // any arbitrary constant will do
+  }</pre></p>
+
+    
+<h3><a name="HE_INHERITS_EQUALS_USE_HASHCODE">HE: Class inherits equals() and uses Object.hashCode() (HE_INHERITS_EQUALS_USE_HASHCODE)</a></h3>
+
+
+  <p> This class inherits <code>equals(Object)</code> from an abstract
+  superclass, and <code>hashCode()</code> from
+<code>java.lang.Object</code> (which returns
+  the identity hash code, an arbitrary value assigned to the object
+  by the VM).&nbsp; Therefore, the class is very likely to violate the
+  invariant that equal objects must have equal hashcodes.</p>
+
+  <p>If you don't want to define a hashCode method, and/or don't
+   believe the object will ever be put into a HashMap/Hashtable,
+   define the <code>hashCode()</code> method
+   to throw <code>UnsupportedOperationException</code>.</p>
+
+    
+<h3><a name="IC_SUPERCLASS_USES_SUBCLASS_DURING_INITIALIZATION">IC: Superclass uses subclass during initialization (IC_SUPERCLASS_USES_SUBCLASS_DURING_INITIALIZATION)</a></h3>
+
+
+  <p> During the initialization of a class, the class makes an active use of a subclass.
+That subclass will not yet be initialized at the time of this use.
+For example, in the following code, <code>foo</code> will be null.</p>
+
+<pre>
+public class CircularClassInitialization {
+    static class InnerClassSingleton extends CircularClassInitialization {
+        static InnerClassSingleton singleton = new InnerClassSingleton();
+    }
+
+    static CircularClassInitialization foo = InnerClassSingleton.singleton;
+}
+</pre>
+
+
+    
+<h3><a name="IMSE_DONT_CATCH_IMSE">IMSE: Dubious catching of IllegalMonitorStateException (IMSE_DONT_CATCH_IMSE)</a></h3>
+
+
+<p>IllegalMonitorStateException is generally only
+   thrown in case of a design flaw in your code (calling wait or
+   notify on an object you do not hold a lock on).</p>
+
+    
+<h3><a name="ISC_INSTANTIATE_STATIC_CLASS">ISC: Needless instantiation of class that only supplies static methods (ISC_INSTANTIATE_STATIC_CLASS)</a></h3>
+
+
+<p> This class allocates an object that is based on a class that only supplies static methods. This object
+does not need to be created, just access the static methods directly using the class name as a qualifier.</p>
+
+        
+<h3><a name="IT_NO_SUCH_ELEMENT">It: Iterator next() method can't throw NoSuchElementException (IT_NO_SUCH_ELEMENT)</a></h3>
+
+
+  <p> This class implements the <code>java.util.Iterator</code> interface.&nbsp;
+  However, its <code>next()</code> method is not capable of throwing
+  <code>java.util.NoSuchElementException</code>.&nbsp; The <code>next()</code>
+  method should be changed so it throws <code>NoSuchElementException</code>
+  if is called when there are no more elements to return.</p>
+
+    
+<h3><a name="J2EE_STORE_OF_NON_SERIALIZABLE_OBJECT_INTO_SESSION">J2EE: Store of non serializable object into HttpSession (J2EE_STORE_OF_NON_SERIALIZABLE_OBJECT_INTO_SESSION)</a></h3>
+
+
+<p>
+This code seems to be storing a non-serializable object into an HttpSession.
+If this session is passivated or migrated, an error will result.
+</p>
+
+    
+<h3><a name="JCIP_FIELD_ISNT_FINAL_IN_IMMUTABLE_CLASS">JCIP: Fields of immutable classes should be final (JCIP_FIELD_ISNT_FINAL_IN_IMMUTABLE_CLASS)</a></h3>
+
+
+  <p> The class is annotated with net.jcip.annotations.Immutable, and the rules for that annotation require
+that all fields are final.
+   .</p>
+
+    
+<h3><a name="NP_BOOLEAN_RETURN_NULL">NP: Method with Boolean return type returns explicit null (NP_BOOLEAN_RETURN_NULL)</a></h3>
+
+       
+       <p>
+    A method that returns either Boolean.TRUE, Boolean.FALSE or null is an accident waiting to happen.
+    This method can be invoked as though it returned a value of type boolean, and
+    the compiler will insert automatic unboxing of the Boolean value. If a null value is returned,
+    this will result in a NullPointerException.
+       </p>
+       
+       
+<h3><a name="NP_CLONE_COULD_RETURN_NULL">NP: Clone method may return null (NP_CLONE_COULD_RETURN_NULL)</a></h3>
+
+      
+      <p>
+    This clone method seems to return null in some circumstances, but clone is never
+    allowed to return a null value.  If you are convinced this path is unreachable, throw an AssertionError
+    instead.
+      </p>
+      
+   
+<h3><a name="NP_EQUALS_SHOULD_HANDLE_NULL_ARGUMENT">NP: equals() method does not check for null argument (NP_EQUALS_SHOULD_HANDLE_NULL_ARGUMENT)</a></h3>
+
+      
+      <p>
+      This implementation of equals(Object) violates the contract defined
+      by java.lang.Object.equals() because it does not check for null
+      being passed as the argument.  All equals() methods should return
+      false if passed a null value.
+      </p>
+      
+   
+<h3><a name="NP_TOSTRING_COULD_RETURN_NULL">NP: toString method may return null (NP_TOSTRING_COULD_RETURN_NULL)</a></h3>
+
+      
+      <p>
+    This toString method seems to return null in some circumstances. A liberal reading of the
+    spec could be interpreted as allowing this, but it is probably a bad idea and could cause
+    other code to break. Return the empty string or some other appropriate string rather than null.
+      </p>
+      
+   
+<h3><a name="NM_CLASS_NAMING_CONVENTION">Nm: Class names should start with an upper case letter (NM_CLASS_NAMING_CONVENTION)</a></h3>
+
+
+  <p> Class names should be nouns, in mixed case with the first letter of each internal word capitalized. Try to keep your class names simple and descriptive. Use whole words-avoid acronyms and abbreviations (unless the abbreviation is much more widely used than the long form, such as URL or HTML).
+</p>
+
+    
+<h3><a name="NM_CLASS_NOT_EXCEPTION">Nm: Class is not derived from an Exception, even though it is named as such (NM_CLASS_NOT_EXCEPTION)</a></h3>
+
+
+<p> This class is not derived from another exception, but ends with 'Exception'. This will
+be confusing to users of this class.</p>
+
+    
+<h3><a name="NM_CONFUSING">Nm: Confusing method names (NM_CONFUSING)</a></h3>
+
+
+  <p> The referenced methods have names that differ only by capitalization.</p>
+
+    
+<h3><a name="NM_FIELD_NAMING_CONVENTION">Nm: Field names should start with a lower case letter (NM_FIELD_NAMING_CONVENTION)</a></h3>
+
+
+  <p>
+Names of fields that are not final should be in mixed case with a lowercase first letter and the first letters of subsequent words capitalized.
+</p>
+
+    
+<h3><a name="NM_FUTURE_KEYWORD_USED_AS_IDENTIFIER">Nm: Use of identifier that is a keyword in later versions of Java (NM_FUTURE_KEYWORD_USED_AS_IDENTIFIER)</a></h3>
+
+
+<p>The identifier is a word that is reserved as a keyword in later versions of Java, and your code will need to be changed
+in order to compile it in later versions of Java.</p>
+
+
+    
+<h3><a name="NM_FUTURE_KEYWORD_USED_AS_MEMBER_IDENTIFIER">Nm: Use of identifier that is a keyword in later versions of Java (NM_FUTURE_KEYWORD_USED_AS_MEMBER_IDENTIFIER)</a></h3>
+
+
+<p>This identifier is used as a keyword in later versions of Java. This code, and
+any code that references this API,
+will need to be changed in order to compile it in later versions of Java.</p>
+
+
+    
+<h3><a name="NM_METHOD_NAMING_CONVENTION">Nm: Method names should start with a lower case letter (NM_METHOD_NAMING_CONVENTION)</a></h3>
+
+
+  <p>
+Methods should be verbs, in mixed case with the first letter lowercase, with the first letter of each internal word capitalized.
+</p>
+
+    
+<h3><a name="NM_SAME_SIMPLE_NAME_AS_INTERFACE">Nm: Class names shouldn't shadow simple name of implemented interface (NM_SAME_SIMPLE_NAME_AS_INTERFACE)</a></h3>
+
+
+  <p> This class/interface has a simple name that is identical to that of an implemented/extended interface, except
+that the interface is in a different package (e.g., <code>alpha.Foo</code> extends <code>beta.Foo</code>).
+This can be exceptionally confusing, create lots of situations in which you have to look at import statements
+to resolve references and creates many
+opportunities to accidently define methods that do not override methods in their superclasses.
+</p>
+
+    
+<h3><a name="NM_SAME_SIMPLE_NAME_AS_SUPERCLASS">Nm: Class names shouldn't shadow simple name of superclass (NM_SAME_SIMPLE_NAME_AS_SUPERCLASS)</a></h3>
+
+
+  <p> This class has a simple name that is identical to that of its superclass, except
+that its superclass is in a different package (e.g., <code>alpha.Foo</code> extends <code>beta.Foo</code>).
+This can be exceptionally confusing, create lots of situations in which you have to look at import statements
+to resolve references and creates many
+opportunities to accidently define methods that do not override methods in their superclasses.
+</p>
+
+    
+<h3><a name="NM_VERY_CONFUSING_INTENTIONAL">Nm: Very confusing method names (but perhaps intentional) (NM_VERY_CONFUSING_INTENTIONAL)</a></h3>
+
+
+  <p> The referenced methods have names that differ only by capitalization.
+This is very confusing because if the capitalization were
+identical then one of the methods would override the other. From the existence of other methods, it
+seems that the existence of both of these methods is intentional, but is sure is confusing.
+You should try hard to eliminate one of them, unless you are forced to have both due to frozen APIs.
+</p>
+
+    
+<h3><a name="NM_WRONG_PACKAGE_INTENTIONAL">Nm: Method doesn't override method in superclass due to wrong package for parameter (NM_WRONG_PACKAGE_INTENTIONAL)</a></h3>
+
+
+  <p> The method in the subclass doesn't override a similar method in a superclass because the type of a parameter doesn't exactly match
+the type of the corresponding parameter in the superclass. For example, if you have:</p>
+
+<blockquote>
+<pre>
+import alpha.Foo;
+public class A {
+  public int f(Foo x) { return 17; }
+}
+----
+import beta.Foo;
+public class B extends A {
+  public int f(Foo x) { return 42; }
+  public int f(alpha.Foo x) { return 27; }
+}
+</pre>
+</blockquote>
+
+<p>The <code>f(Foo)</code> method defined in class <code>B</code> doesn't
+override the
+<code>f(Foo)</code> method defined in class <code>A</code>, because the argument
+types are <code>Foo</code>'s from different packages.
+</p>
+
+<p>In this case, the subclass does define a method with a signature identical to the method in the superclass,
+so this is presumably understood. However, such methods are exceptionally confusing. You should strongly consider
+removing or deprecating the method with the similar but not identical signature.
+</p>
+
+    
+<h3><a name="ODR_OPEN_DATABASE_RESOURCE">ODR: Method may fail to close database resource (ODR_OPEN_DATABASE_RESOURCE)</a></h3>
+
+
+<p> The method creates a database resource (such as a database connection
+or row set), does not assign it to any
+fields, pass it to other methods, or return it, and does not appear to close
+the object on all paths out of the method.&nbsp; Failure to
+close database resources on all paths out of a method may
+result in poor performance, and could cause the application to
+have problems communicating with the database.
+</p>
+
+    
+<h3><a name="ODR_OPEN_DATABASE_RESOURCE_EXCEPTION_PATH">ODR: Method may fail to close database resource on exception (ODR_OPEN_DATABASE_RESOURCE_EXCEPTION_PATH)</a></h3>
+
+
+<p> The method creates a database resource (such as a database connection
+or row set), does not assign it to any
+fields, pass it to other methods, or return it, and does not appear to close
+the object on all exception paths out of the method.&nbsp; Failure to
+close database resources on all paths out of a method may
+result in poor performance, and could cause the application to
+have problems communicating with the database.</p>
+
+    
+<h3><a name="OS_OPEN_STREAM">OS: Method may fail to close stream (OS_OPEN_STREAM)</a></h3>
+
+
+<p> The method creates an IO stream object, does not assign it to any
+fields, pass it to other methods that might close it,
+or return it, and does not appear to close
+the stream on all paths out of the method.&nbsp; This may result in
+a file descriptor leak.&nbsp; It is generally a good
+idea to use a <code>finally</code> block to ensure that streams are
+closed.</p>
+
+    
+<h3><a name="OS_OPEN_STREAM_EXCEPTION_PATH">OS: Method may fail to close stream on exception (OS_OPEN_STREAM_EXCEPTION_PATH)</a></h3>
+
+
+<p> The method creates an IO stream object, does not assign it to any
+fields, pass it to other methods, or return it, and does not appear to close
+it on all possible exception paths out of the method.&nbsp;
+This may result in a file descriptor leak.&nbsp; It is generally a good
+idea to use a <code>finally</code> block to ensure that streams are
+closed.</p>
+
+    
+<h3><a name="PZ_DONT_REUSE_ENTRY_OBJECTS_IN_ITERATORS">PZ: Don't reuse entry objects in iterators (PZ_DONT_REUSE_ENTRY_OBJECTS_IN_ITERATORS)</a></h3>
+
+     
+     <p> The entrySet() method is allowed to return a view of the
+     underlying Map in which an Iterator and Map.Entry. This clever
+     idea was used in several Map implementations, but introduces the possibility
+     of nasty coding mistakes. If a map <code>m</code> returns
+     such an iterator for an entrySet, then
+     <code>c.addAll(m.entrySet())</code> will go badly wrong. All of
+     the Map implementations in OpenJDK 1.7 have been rewritten to avoid this,
+     you should to.
+    </p>
+     
+    
+<h3><a name="RC_REF_COMPARISON_BAD_PRACTICE">RC: Suspicious reference comparison to constant (RC_REF_COMPARISON_BAD_PRACTICE)</a></h3>
+
+
+<p> This method compares a reference value to a constant using the == or != operator,
+where the correct way to compare instances of this type is generally
+with the equals() method.
+It is possible to create distinct instances that are equal but do not compare as == since
+they are different objects.
+Examples of classes which should generally
+not be compared by reference are java.lang.Integer, java.lang.Float, etc.</p>
+
+    
+<h3><a name="RC_REF_COMPARISON_BAD_PRACTICE_BOOLEAN">RC: Suspicious reference comparison of Boolean values (RC_REF_COMPARISON_BAD_PRACTICE_BOOLEAN)</a></h3>
+
+
+<p> This method compares two Boolean values using the == or != operator.
+Normally, there are only two Boolean values (Boolean.TRUE and Boolean.FALSE),
+but it is possible to create other Boolean objects using the <code>new Boolean(b)</code>
+constructor. It is best to avoid such objects, but if they do exist,
+then checking Boolean objects for equality using == or != will give results
+than are different than you would get using <code>.equals(...)</code>
+</p>
+
+    
+<h3><a name="RR_NOT_CHECKED">RR: Method ignores results of InputStream.read() (RR_NOT_CHECKED)</a></h3>
+
+
+  <p> This method ignores the return value of one of the variants of
+  <code>java.io.InputStream.read()</code> which can return multiple bytes.&nbsp;
+  If the return value is not checked, the caller will not be able to correctly
+  handle the case where fewer bytes were read than the caller requested.&nbsp;
+  This is a particularly insidious kind of bug, because in many programs,
+  reads from input streams usually do read the full amount of data requested,
+  causing the program to fail only sporadically.</p>
+
+    
+<h3><a name="SR_NOT_CHECKED">RR: Method ignores results of InputStream.skip() (SR_NOT_CHECKED)</a></h3>
+
+
+  <p> This method ignores the return value of
+  <code>java.io.InputStream.skip()</code> which can skip multiple bytes.&nbsp;
+  If the return value is not checked, the caller will not be able to correctly
+  handle the case where fewer bytes were skipped than the caller requested.&nbsp;
+  This is a particularly insidious kind of bug, because in many programs,
+  skips from input streams usually do skip the full amount of data requested,
+  causing the program to fail only sporadically. With Buffered streams, however,
+  skip() will only skip data in the buffer, and will routinely fail to skip the
+  requested number of bytes.</p>
+
+    
+<h3><a name="RV_NEGATING_RESULT_OF_COMPARETO">RV: Negating the result of compareTo()/compare() (RV_NEGATING_RESULT_OF_COMPARETO)</a></h3>
+
+
+  <p> This code negatives the return value of a compareTo or compare method.
+This is a questionable or bad programming practice, since if the return
+value is Integer.MIN_VALUE, negating the return value won't
+negate the sign of the result. You can achieve the same intended result
+by reversing the order of the operands rather than by negating the results.
+</p>
+
+    
+<h3><a name="RV_RETURN_VALUE_IGNORED_BAD_PRACTICE">RV: Method ignores exceptional return value (RV_RETURN_VALUE_IGNORED_BAD_PRACTICE)</a></h3>
+
+
+   <p> This method returns a value that is not checked. The return value should be checked
+since it can indicate an unusual or unexpected function execution. For
+example, the <code>File.delete()</code> method returns false
+if the file could not be successfully deleted (rather than
+throwing an Exception).
+If you don't check the result, you won't notice if the method invocation
+signals unexpected behavior by returning an atypical return value.
+</p>
+
+    
+<h3><a name="SI_INSTANCE_BEFORE_FINALS_ASSIGNED">SI: Static initializer creates instance before all static final fields assigned (SI_INSTANCE_BEFORE_FINALS_ASSIGNED)</a></h3>
+
+
+<p> The class's static initializer creates an instance of the class
+before all of the static final fields are assigned.</p>
+
+    
+<h3><a name="SW_SWING_METHODS_INVOKED_IN_SWING_THREAD">SW: Certain swing methods needs to be invoked in Swing thread (SW_SWING_METHODS_INVOKED_IN_SWING_THREAD)</a></h3>
+
+
+<p>(<a href="http://web.archive.org/web/20090526170426/http://java.sun.com/developer/JDCTechTips/2003/tt1208.html">From JDC Tech Tip</a>): The Swing methods
+show(), setVisible(), and pack() will create the associated peer for the frame.
+With the creation of the peer, the system creates the event dispatch thread.
+This makes things problematic because the event dispatch thread could be notifying
+listeners while pack and validate are still processing. This situation could result in
+two threads going through the Swing component-based GUI -- it's a serious flaw that
+could result in deadlocks or other related threading issues. A pack call causes
+components to be realized. As they are being realized (that is, not necessarily
+visible), they could trigger listener notification on the event dispatch thread.</p>
+
+
+    
+<h3><a name="SE_BAD_FIELD">Se: Non-transient non-serializable instance field in serializable class (SE_BAD_FIELD)</a></h3>
+
+
+<p> This Serializable class defines a non-primitive instance field which is neither transient,
+Serializable, or <code>java.lang.Object</code>, and does not appear to implement
+the <code>Externalizable</code> interface or the
+<code>readObject()</code> and <code>writeObject()</code> methods.&nbsp;
+Objects of this class will not be deserialized correctly if a non-Serializable
+object is stored in this field.</p>
+
+    
+<h3><a name="SE_BAD_FIELD_INNER_CLASS">Se: Non-serializable class has a serializable inner class (SE_BAD_FIELD_INNER_CLASS)</a></h3>
+
+
+<p> This Serializable class is an inner class of a non-serializable class.
+Thus, attempts to serialize it will also attempt to associate instance of the outer
+class with which it is associated, leading to a runtime error.
+</p>
+<p>If possible, making the inner class a static inner class should solve the
+problem. Making the outer class serializable might also work, but that would
+mean serializing an instance of the inner class would always also serialize the instance
+of the outer class, which it often not what you really want.
+
+    
+<h3><a name="SE_BAD_FIELD_STORE">Se: Non-serializable value stored into instance field of a serializable class (SE_BAD_FIELD_STORE)</a></h3>
+
+
+<p> A non-serializable value is stored into a non-transient field
+of a serializable class.</p>
+
+    
+<h3><a name="SE_COMPARATOR_SHOULD_BE_SERIALIZABLE">Se: Comparator doesn't implement Serializable (SE_COMPARATOR_SHOULD_BE_SERIALIZABLE)</a></h3>
+
+
+  <p> This class implements the <code>Comparator</code> interface. You
+should consider whether or not it should also implement the <code>Serializable</code>
+interface. If a comparator is used to construct an ordered collection
+such as a <code>TreeMap</code>, then the <code>TreeMap</code>
+will be serializable only if the comparator is also serializable.
+As most comparators have little or no state, making them serializable
+is generally easy and good defensive programming.
+</p>
+
+    
+<h3><a name="SE_INNER_CLASS">Se: Serializable inner class (SE_INNER_CLASS)</a></h3>
+
+
+<p> This Serializable class is an inner class.  Any attempt to serialize
+it will also serialize the associated outer instance. The outer instance is serializable,
+so this won't fail, but it might serialize a lot more data than intended.
+If possible, making the inner class a static inner class (also known as a nested class) should solve the
+problem.
+
+    
+<h3><a name="SE_NONFINAL_SERIALVERSIONID">Se: serialVersionUID isn't final (SE_NONFINAL_SERIALVERSIONID)</a></h3>
+
+
+  <p> This class defines a <code>serialVersionUID</code> field that is not final.&nbsp;
+  The field should be made final
+   if it is intended to specify
+   the version UID for purposes of serialization.</p>
+
+    
+<h3><a name="SE_NONLONG_SERIALVERSIONID">Se: serialVersionUID isn't long (SE_NONLONG_SERIALVERSIONID)</a></h3>
+
+
+  <p> This class defines a <code>serialVersionUID</code> field that is not long.&nbsp;
+  The field should be made long
+   if it is intended to specify
+   the version UID for purposes of serialization.</p>
+
+    
+<h3><a name="SE_NONSTATIC_SERIALVERSIONID">Se: serialVersionUID isn't static (SE_NONSTATIC_SERIALVERSIONID)</a></h3>
+
+
+  <p> This class defines a <code>serialVersionUID</code> field that is not static.&nbsp;
+  The field should be made static
+   if it is intended to specify
+   the version UID for purposes of serialization.</p>
+
+    
+<h3><a name="SE_NO_SUITABLE_CONSTRUCTOR">Se: Class is Serializable but its superclass doesn't define a void constructor (SE_NO_SUITABLE_CONSTRUCTOR)</a></h3>
+
+
+  <p> This class implements the <code>Serializable</code> interface
+   and its superclass does not. When such an object is deserialized,
+   the fields of the superclass need to be initialized by
+   invoking the void constructor of the superclass.
+   Since the superclass does not have one,
+   serialization and deserialization will fail at runtime.</p>
+
+    
+<h3><a name="SE_NO_SUITABLE_CONSTRUCTOR_FOR_EXTERNALIZATION">Se: Class is Externalizable but doesn't define a void constructor (SE_NO_SUITABLE_CONSTRUCTOR_FOR_EXTERNALIZATION)</a></h3>
+
+
+  <p> This class implements the <code>Externalizable</code> interface, but does
+  not define a void constructor. When Externalizable objects are deserialized,
+   they first need to be constructed by invoking the void
+   constructor. Since this class does not have one,
+   serialization and deserialization will fail at runtime.</p>
+
+    
+<h3><a name="SE_READ_RESOLVE_MUST_RETURN_OBJECT">Se: The readResolve method must be declared with a return type of Object.  (SE_READ_RESOLVE_MUST_RETURN_OBJECT)</a></h3>
+
+
+  <p> In order for the readResolve method to be recognized by the serialization
+mechanism, it must be declared to have a return type of Object.
+</p>
+
+    
+<h3><a name="SE_TRANSIENT_FIELD_NOT_RESTORED">Se: Transient field that isn't set by deserialization.  (SE_TRANSIENT_FIELD_NOT_RESTORED)</a></h3>
+
+
+  <p> This class contains a field that is updated at multiple places in the class, thus it seems to be part of the state of the class. However, since the field is marked as transient and not set in readObject or readResolve, it will contain the default value in any
+deserialized instance of the class.
+</p>
+
+    
+<h3><a name="SE_NO_SERIALVERSIONID">SnVI: Class is Serializable, but doesn't define serialVersionUID (SE_NO_SERIALVERSIONID)</a></h3>
+
+
+  <p> This class implements the <code>Serializable</code> interface, but does
+  not define a <code>serialVersionUID</code> field.&nbsp;
+  A change as simple as adding a reference to a .class object
+    will add synthetic fields to the class,
+   which will unfortunately change the implicit
+   serialVersionUID (e.g., adding a reference to <code>String.class</code>
+   will generate a static field <code>class$java$lang$String</code>).
+   Also, different source code to bytecode compilers may use different
+   naming conventions for synthetic variables generated for
+   references to class objects or inner classes.
+   To ensure interoperability of Serializable across versions,
+   consider adding an explicit serialVersionUID.</p>
+
+    
+<h3><a name="UI_INHERITANCE_UNSAFE_GETRESOURCE">UI: Usage of GetResource may be unsafe if class is extended (UI_INHERITANCE_UNSAFE_GETRESOURCE)</a></h3>
+
+
+<p>Calling <code>this.getClass().getResource(...)</code> could give
+results other than expected if this class is extended by a class in
+another package.</p>
+
+    
+<h3><a name="BC_IMPOSSIBLE_CAST">BC: Impossible cast (BC_IMPOSSIBLE_CAST)</a></h3>
+
+
+<p>
+This cast will always throw a ClassCastException.
+FindBugs tracks type information from instanceof checks,
+and also uses more precise information about the types
+of values returned from methods and loaded from fields.
+Thus, it may have more precise information that just
+the declared type of a variable, and can use this to determine
+that a cast will always throw an exception at runtime.
+
+</p>
+
+    
+<h3><a name="BC_IMPOSSIBLE_DOWNCAST">BC: Impossible downcast (BC_IMPOSSIBLE_DOWNCAST)</a></h3>
+
+
+<p>
+This cast will always throw a ClassCastException.
+The analysis believes it knows
+the precise type of the value being cast, and the attempt to
+downcast it to a subtype will always fail by throwing a ClassCastException.
+</p>
+
+    
+<h3><a name="BC_IMPOSSIBLE_DOWNCAST_OF_TOARRAY">BC: Impossible downcast of toArray() result (BC_IMPOSSIBLE_DOWNCAST_OF_TOARRAY)</a></h3>
+
+
+<p>
+This code is casting the result of calling <code>toArray()</code> on a collection
+to a type more specific than <code>Object[]</code>, as in:
+<pre>
+String[] getAsArray(Collection&lt;String&gt; c) {
+  return (String[]) c.toArray();
+  }
+</pre>
+<p>This will usually fail by throwing a ClassCastException. The <code>toArray()</code>
+of almost all collections return an <code>Object[]</code>. They can't really do anything else,
+since the Collection object has no reference to the declared generic type of the collection.
+<p>The correct way to do get an array of a specific type from a collection is to use
+  <code>c.toArray(new String[]);</code>
+  or <code>c.toArray(new String[c.size()]);</code> (the latter is slightly more efficient).
+<p>There is one common/known exception exception to this. The <code>toArray()</code>
+method of lists returned by <code>Arrays.asList(...)</code> will return a covariantly
+typed array. For example, <code>Arrays.asArray(new String[] { "a" }).toArray()</code>
+will return a <code>String []</code>. FindBugs attempts to detect and suppress
+such cases, but may miss some.
+</p>
+
+    
+<h3><a name="BC_IMPOSSIBLE_INSTANCEOF">BC: instanceof will always return false (BC_IMPOSSIBLE_INSTANCEOF)</a></h3>
+
+
+<p>
+This instanceof test will always return false. Although this is safe, make sure it isn't
+an indication of some misunderstanding or some other logic error.
+</p>
+
+    
+<h3><a name="BIT_ADD_OF_SIGNED_BYTE">BIT: Bitwise add of signed byte value (BIT_ADD_OF_SIGNED_BYTE)</a></h3>
+
+
+<p> Adds a byte value and a value which is known to have the 8 lower bits clear.
+Values loaded from a byte array are sign extended to 32 bits
+before any any bitwise operations are performed on the value.
+Thus, if <code>b[0]</code> contains the value <code>0xff</code>, and
+<code>x</code> is initially 0, then the code
+<code>((x &lt;&lt; 8) + b[0])</code>  will sign extend <code>0xff</code>
+to get <code>0xffffffff</code>, and thus give the value
+<code>0xffffffff</code> as the result.
+</p>
+
+<p>In particular, the following code for packing a byte array into an int is badly wrong: </p>
+<pre>
+int result = 0;
+for(int i = 0; i &lt; 4; i++)
+  result = ((result &lt;&lt; 8) + b[i]);
+</pre>
+
+<p>The following idiom will work instead: </p>
+<pre>
+int result = 0;
+for(int i = 0; i &lt; 4; i++)
+  result = ((result &lt;&lt; 8) + (b[i] &amp; 0xff));
+</pre>
+
+
+    
+<h3><a name="BIT_AND">BIT: Incompatible bit masks (BIT_AND)</a></h3>
+
+
+<p> This method compares an expression of the form (e &amp; C) to D,
+which will always compare unequal
+due to the specific values of constants C and D.
+This may indicate a logic error or typo.</p>
+
+    
+<h3><a name="BIT_AND_ZZ">BIT: Check to see if ((...) & 0) == 0 (BIT_AND_ZZ)</a></h3>
+
+
+<p> This method compares an expression of the form (e &amp; 0) to 0,
+which will always compare equal.
+This may indicate a logic error or typo.</p>
+
+    
+<h3><a name="BIT_IOR">BIT: Incompatible bit masks (BIT_IOR)</a></h3>
+
+
+<p> This method compares an expression of the form (e | C) to D.
+which will always compare unequal
+due to the specific values of constants C and D.
+This may indicate a logic error or typo.</p>
+
+<p> Typically, this bug occurs because the code wants to perform
+a membership test in a bit set, but uses the bitwise OR
+operator ("|") instead of bitwise AND ("&amp;").</p>
+
+    
+<h3><a name="BIT_IOR_OF_SIGNED_BYTE">BIT: Bitwise OR of signed byte value (BIT_IOR_OF_SIGNED_BYTE)</a></h3>
+
+
+<p> Loads a byte value (e.g., a value loaded from a byte array or returned by a method
+with return type byte)  and performs a bitwise OR with
+that value. Byte values are sign extended to 32 bits
+before any any bitwise operations are performed on the value.
+Thus, if <code>b[0]</code> contains the value <code>0xff</code>, and
+<code>x</code> is initially 0, then the code
+<code>((x &lt;&lt; 8) | b[0])</code>  will sign extend <code>0xff</code>
+to get <code>0xffffffff</code>, and thus give the value
+<code>0xffffffff</code> as the result.
+</p>
+
+<p>In particular, the following code for packing a byte array into an int is badly wrong: </p>
+<pre>
+int result = 0;
+for(int i = 0; i &lt; 4; i++)
+  result = ((result &lt;&lt; 8) | b[i]);
+</pre>
+
+<p>The following idiom will work instead: </p>
+<pre>
+int result = 0;
+for(int i = 0; i &lt; 4; i++)
+  result = ((result &lt;&lt; 8) | (b[i] &amp; 0xff));
+</pre>
+
+
+    
+<h3><a name="BIT_SIGNED_CHECK_HIGH_BIT">BIT: Check for sign of bitwise operation (BIT_SIGNED_CHECK_HIGH_BIT)</a></h3>
+
+
+<p> This method compares an expression such as
+<pre>((event.detail &amp; SWT.SELECTED) &gt; 0)</pre>.
+Using bit arithmetic and then comparing with the greater than operator can
+lead to unexpected results (of course depending on the value of
+SWT.SELECTED). If SWT.SELECTED is a negative number, this is a candidate
+for a bug. Even when SWT.SELECTED is not negative, it seems good practice
+to use '!= 0' instead of '&gt; 0'.
+</p>
+<p>
+<em>Boris Bokowski</em>
+</p>
+
+    
+<h3><a name="BOA_BADLY_OVERRIDDEN_ADAPTER">BOA: Class overrides a method implemented in super class Adapter wrongly (BOA_BADLY_OVERRIDDEN_ADAPTER)</a></h3>
+
+
+<p> This method overrides a method found in a parent class, where that class is an Adapter that implements
+a listener defined in the java.awt.event or javax.swing.event package. As a result, this method will not
+get called when the event occurs.</p>
+
+    
+<h3><a name="ICAST_BAD_SHIFT_AMOUNT">BSHIFT: 32 bit int shifted by an amount not in the range 0..31 (ICAST_BAD_SHIFT_AMOUNT)</a></h3>
+
+
+<p>
+The code performs shift of a 32 bit int by a constant amount outside
+the range 0..31.
+The effect of this is to use the lower 5 bits of the integer
+value to decide how much to shift by (e.g., shifting by 40 bits is the same as shifting by 8 bits,
+and shifting by 32 bits is the same as shifting by zero bits). This probably isn't what was expected,
+and it is at least confusing.
+</p>
+
+    
+<h3><a name="BX_UNBOXED_AND_COERCED_FOR_TERNARY_OPERATOR">Bx: Primitive value is unboxed and coerced for ternary operator (BX_UNBOXED_AND_COERCED_FOR_TERNARY_OPERATOR)</a></h3>
+
+
+  <p>A wrapped primitive value is unboxed and converted to another primitive type as part of the
+evaluation of a conditional ternary operator (the <code> b ? e1 : e2</code> operator). The
+semantics of Java mandate that if <code>e1</code> and <code>e2</code> are wrapped
+numeric values, the values are unboxed and converted/coerced to their common type (e.g,
+if <code>e1</code> is of type <code>Integer</code>
+and <code>e2</code> is of type <code>Float</code>, then <code>e1</code> is unboxed,
+converted to a floating point value, and boxed. See JLS Section 15.25.
+</p>
+
+    
+<h3><a name="CO_COMPARETO_RESULTS_MIN_VALUE">Co: compareTo()/compare() returns Integer.MIN_VALUE (CO_COMPARETO_RESULTS_MIN_VALUE)</a></h3>
+
+
+  <p> In some situation, this compareTo or compare method returns
+the  constant Integer.MIN_VALUE, which is an exceptionally bad practice.
+  The only thing that matters about the return value of compareTo is the sign of the result.
+    But people will sometimes negate the return value of compareTo, expecting that this will negate
+    the sign of the result. And it will, except in the case where the value returned is Integer.MIN_VALUE.
+    So just return -1 rather than Integer.MIN_VALUE.
+
+    
+<h3><a name="DLS_DEAD_STORE_OF_CLASS_LITERAL">DLS: Dead store of class literal (DLS_DEAD_STORE_OF_CLASS_LITERAL)</a></h3>
+
+
+<p>
+This instruction assigns a class literal to a variable and then never uses it.
+<a href="//java.sun.com/j2se/1.5.0/compatibility.html#literal">The behavior of this differs in Java 1.4 and in Java 5.</a>
+In Java 1.4 and earlier, a reference to <code>Foo.class</code> would force the static initializer
+for <code>Foo</code> to be executed, if it has not been executed already.
+In Java 5 and later, it does not.
+</p>
+<p>See Sun's <a href="//java.sun.com/j2se/1.5.0/compatibility.html#literal">article on Java SE compatibility</a>
+for more details and examples, and suggestions on how to force class initialization in Java 5.
+</p>
+
+    
+<h3><a name="DLS_OVERWRITTEN_INCREMENT">DLS: Overwritten increment (DLS_OVERWRITTEN_INCREMENT)</a></h3>
+
+
+<p>
+The code performs an increment operation (e.g., <code>i++</code>) and then
+immediately overwrites it. For example, <code>i = i++</code> immediately
+overwrites the incremented value with the original value.
+</p>
+
+    
+<h3><a name="DMI_ARGUMENTS_WRONG_ORDER">DMI: Reversed method arguments (DMI_ARGUMENTS_WRONG_ORDER)</a></h3>
+
+
+<p> The arguments to this method call seem to be in the wrong order.
+For example, a call <code>Preconditions.checkNotNull("message", message)</code>
+has reserved arguments: the value to be checked is the first argument.
+</p>
+
+    
+<h3><a name="DMI_BAD_MONTH">DMI: Bad constant value for month (DMI_BAD_MONTH)</a></h3>
+
+
+<p>
+This code passes a constant month
+value outside the expected range of 0..11 to a method.
+</p>
+
+    
+<h3><a name="DMI_BIGDECIMAL_CONSTRUCTED_FROM_DOUBLE">DMI: BigDecimal constructed from double that isn't represented precisely (DMI_BIGDECIMAL_CONSTRUCTED_FROM_DOUBLE)</a></h3>
+
+      
+    <p>
+This code creates a BigDecimal from a double value that doesn't translate well to a
+decimal number.
+For example, one might assume that writing new BigDecimal(0.1) in Java creates a BigDecimal which is exactly equal to 0.1 (an unscaled value of 1, with a scale of 1), but it is actually equal to 0.1000000000000000055511151231257827021181583404541015625.
+You probably want to use the BigDecimal.valueOf(double d) method, which uses the String representation
+of the double to create the BigDecimal (e.g., BigDecimal.valueOf(0.1) gives 0.1).
+</p>
+
+
+    
+<h3><a name="DMI_CALLING_NEXT_FROM_HASNEXT">DMI: hasNext method invokes next (DMI_CALLING_NEXT_FROM_HASNEXT)</a></h3>
+
+
+<p>
+The hasNext() method invokes the next() method. This is almost certainly wrong,
+since the hasNext() method is not supposed to change the state of the iterator,
+and the next method is supposed to change the state of the iterator.
+</p>
+
+    
+<h3><a name="DMI_COLLECTIONS_SHOULD_NOT_CONTAIN_THEMSELVES">DMI: Collections should not contain themselves (DMI_COLLECTIONS_SHOULD_NOT_CONTAIN_THEMSELVES)</a></h3>
+
+     
+     <p> This call to a generic collection's method would only make sense if a collection contained
+itself (e.g., if <code>s.contains(s)</code> were true). This is unlikely to be true and would cause
+problems if it were true (such as the computation of the hash code resulting in infinite recursion).
+It is likely that the wrong value is being passed as a parameter.
+    </p>
+     
+    
+<h3><a name="DMI_DOH">DMI: D'oh! A nonsensical method invocation (DMI_DOH)</a></h3>
+
+      
+    <p>
+This partical method invocation doesn't make sense, for reasons that should be apparent from inspection.
+</p>
+
+
+    
+<h3><a name="DMI_INVOKING_HASHCODE_ON_ARRAY">DMI: Invocation of hashCode on an array (DMI_INVOKING_HASHCODE_ON_ARRAY)</a></h3>
+
+
+<p>
+The code invokes hashCode on an array. Calling hashCode on
+an array returns the same value as System.identityHashCode, and ingores
+the contents and length of the array. If you need a hashCode that
+depends on the contents of an array <code>a</code>,
+use <code>java.util.Arrays.hashCode(a)</code>.
+
+</p>
+
+    
+<h3><a name="DMI_LONG_BITS_TO_DOUBLE_INVOKED_ON_INT">DMI: Double.longBitsToDouble invoked on an int (DMI_LONG_BITS_TO_DOUBLE_INVOKED_ON_INT)</a></h3>
+
+
+<p> The Double.longBitsToDouble method is invoked, but a 32 bit int value is passed
+    as an argument. This almostly certainly is not intended and is unlikely
+    to give the intended result.
+</p>
+
+    
+<h3><a name="DMI_VACUOUS_SELF_COLLECTION_CALL">DMI: Vacuous call to collections (DMI_VACUOUS_SELF_COLLECTION_CALL)</a></h3>
+
+     
+     <p> This call doesn't make sense. For any collection <code>c</code>, calling <code>c.containsAll(c)</code> should
+always be true, and <code>c.retainAll(c)</code> should have no effect.
+    </p>
+     
+    
+<h3><a name="DMI_ANNOTATION_IS_NOT_VISIBLE_TO_REFLECTION">Dm: Can't use reflection to check for presence of annotation without runtime retention (DMI_ANNOTATION_IS_NOT_VISIBLE_TO_REFLECTION)</a></h3>
+
+
+  <p> Unless an annotation has itself been annotated with  @Retention(RetentionPolicy.RUNTIME), the annotation can't be observed using reflection
+(e.g., by using the isAnnotationPresent method).
+   .</p>
+
+    
+<h3><a name="DMI_FUTILE_ATTEMPT_TO_CHANGE_MAXPOOL_SIZE_OF_SCHEDULED_THREAD_POOL_EXECUTOR">Dm: Futile attempt to change max pool size of ScheduledThreadPoolExecutor (DMI_FUTILE_ATTEMPT_TO_CHANGE_MAXPOOL_SIZE_OF_SCHEDULED_THREAD_POOL_EXECUTOR)</a></h3>
+
+      
+    <p>(<a href="http://java.sun.com/javase/6/docs/api/java/util/concurrent/ScheduledThreadPoolExecutor.html">Javadoc</a>)
+While ScheduledThreadPoolExecutor inherits from ThreadPoolExecutor, a few of the inherited tuning methods are not useful for it. In particular, because it acts as a fixed-sized pool using corePoolSize threads and an unbounded queue, adjustments to maximumPoolSize have no useful effect.
+    </p>
+
+
+    
+<h3><a name="DMI_SCHEDULED_THREAD_POOL_EXECUTOR_WITH_ZERO_CORE_THREADS">Dm: Creation of ScheduledThreadPoolExecutor with zero core threads (DMI_SCHEDULED_THREAD_POOL_EXECUTOR_WITH_ZERO_CORE_THREADS)</a></h3>
+
+      
+    <p>(<a href="http://java.sun.com/javase/6/docs/api/java/util/concurrent/ScheduledThreadPoolExecutor.html#ScheduledThreadPoolExecutor(int)">Javadoc</a>)
+A ScheduledThreadPoolExecutor with zero core threads will never execute anything; changes to the max pool size are ignored.
+</p>
+
+
+    
+<h3><a name="DMI_VACUOUS_CALL_TO_EASYMOCK_METHOD">Dm: Useless/vacuous call to EasyMock method (DMI_VACUOUS_CALL_TO_EASYMOCK_METHOD)</a></h3>
+
+      
+    <p>This call doesn't pass any objects to the EasyMock method, so the call doesn't do anything.
+</p>
+
+
+    
+<h3><a name="EC_ARRAY_AND_NONARRAY">EC: equals() used to compare array and nonarray (EC_ARRAY_AND_NONARRAY)</a></h3>
+
+
+<p>
+This method invokes the .equals(Object o) to compare an array and a reference that doesn't seem
+to be an array. If things being compared are of different types, they are guaranteed to be unequal
+and the comparison is almost certainly an error. Even if they are both arrays, the equals method
+on arrays only determines of the two arrays are the same object.
+To compare the
+contents of the arrays, use java.util.Arrays.equals(Object[], Object[]).
+</p>
+
+    
+<h3><a name="EC_BAD_ARRAY_COMPARE">EC: Invocation of equals() on an array, which is equivalent to == (EC_BAD_ARRAY_COMPARE)</a></h3>
+
+
+<p>
+This method invokes the .equals(Object o) method on an array. Since arrays do not override the equals
+method of Object, calling equals on an array is the same as comparing their addresses. To compare the
+contents of the arrays, use <code>java.util.Arrays.equals(Object[], Object[])</code>.
+To compare the addresses of the arrays, it would be
+less confusing to explicitly check pointer equality using <code>==</code>.
+</p>
+
+    
+<h3><a name="EC_INCOMPATIBLE_ARRAY_COMPARE">EC: equals(...) used to compare incompatible arrays (EC_INCOMPATIBLE_ARRAY_COMPARE)</a></h3>
+
+
+<p>
+This method invokes the .equals(Object o) to compare two arrays, but the arrays of
+of incompatible types (e.g., String[] and StringBuffer[], or String[] and int[]).
+They will never be equal. In addition, when equals(...) is used to compare arrays it
+only checks to see if they are the same array, and ignores the contents of the arrays.
+</p>
+
+    
+<h3><a name="EC_NULL_ARG">EC: Call to equals(null) (EC_NULL_ARG)</a></h3>
+
+
+<p> This method calls equals(Object), passing a null value as
+the argument. According to the contract of the equals() method,
+this call should always return <code>false</code>.</p>
+
+    
+<h3><a name="EC_UNRELATED_CLASS_AND_INTERFACE">EC: Call to equals() comparing unrelated class and interface (EC_UNRELATED_CLASS_AND_INTERFACE)</a></h3>
+
+      
+<p>
+This method calls equals(Object) on two references,  one of which is a class
+and the other an interface, where neither the class nor any of its
+non-abstract subclasses implement the interface.
+Therefore, the objects being compared
+are unlikely to be members of the same class at runtime
+(unless some application classes were not analyzed, or dynamic class
+loading can occur at runtime).
+According to the contract of equals(),
+objects of different
+classes should always compare as unequal; therefore, according to the
+contract defined by java.lang.Object.equals(Object),
+the result of this comparison will always be false at runtime.
+</p>
+      
+   
+<h3><a name="EC_UNRELATED_INTERFACES">EC: Call to equals() comparing different interface types (EC_UNRELATED_INTERFACES)</a></h3>
+
+
+<p> This method calls equals(Object) on two references of unrelated
+interface types, where neither is a subtype of the other,
+and there are no known non-abstract classes which implement both interfaces.
+Therefore, the objects being compared
+are unlikely to be members of the same class at runtime
+(unless some application classes were not analyzed, or dynamic class
+loading can occur at runtime).
+According to the contract of equals(),
+objects of different
+classes should always compare as unequal; therefore, according to the
+contract defined by java.lang.Object.equals(Object),
+the result of this comparison will always be false at runtime.
+</p>
+
+    
+<h3><a name="EC_UNRELATED_TYPES">EC: Call to equals() comparing different types (EC_UNRELATED_TYPES)</a></h3>
+
+
+<p> This method calls equals(Object) on two references of different
+class types with no common subclasses.
+Therefore, the objects being compared
+are unlikely to be members of the same class at runtime
+(unless some application classes were not analyzed, or dynamic class
+loading can occur at runtime).
+According to the contract of equals(),
+objects of different
+classes should always compare as unequal; therefore, according to the
+contract defined by java.lang.Object.equals(Object),
+the result of this comparison will always be false at runtime.
+</p>
+
+    
+<h3><a name="EC_UNRELATED_TYPES_USING_POINTER_EQUALITY">EC: Using pointer equality to compare different types (EC_UNRELATED_TYPES_USING_POINTER_EQUALITY)</a></h3>
+
+
+<p> This method uses using pointer equality to compare two references that seem to be of
+different types.  The result of this comparison will always be false at runtime.
+</p>
+
+    
+<h3><a name="EQ_ALWAYS_FALSE">Eq: equals method always returns false (EQ_ALWAYS_FALSE)</a></h3>
+
+
+  <p> This class defines an equals method that always returns false. This means that an object is not equal to itself, and it is impossible to create useful Maps or Sets of this class. More fundamentally, it means
+that equals is not reflexive, one of the requirements of the equals method.</p>
+<p>The likely intended semantics are object identity: that an object is equal to itself. This is the behavior inherited from class <code>Object</code>. If you need to override an equals inherited from a different
+superclass, you can use use:
+<pre>
+public boolean equals(Object o) { return this == o; }
+</pre>
+</p>
+
+    
+<h3><a name="EQ_ALWAYS_TRUE">Eq: equals method always returns true (EQ_ALWAYS_TRUE)</a></h3>
+
+
+  <p> This class defines an equals method that always returns true. This is imaginative, but not very smart.
+Plus, it means that the equals method is not symmetric.
+</p>
+
+    
+<h3><a name="EQ_COMPARING_CLASS_NAMES">Eq: equals method compares class names rather than class objects (EQ_COMPARING_CLASS_NAMES)</a></h3>
+
+
+  <p> This method checks to see if two objects are the same class by checking to see if the names
+of their classes are equal. You can have different classes with the same name if they are loaded by
+different class loaders. Just check to see if the class objects are the same.
+</p>
+
+    
+<h3><a name="EQ_DONT_DEFINE_EQUALS_FOR_ENUM">Eq: Covariant equals() method defined for enum (EQ_DONT_DEFINE_EQUALS_FOR_ENUM)</a></h3>
+
+
+  <p> This class defines an enumeration, and equality on enumerations are defined
+using object identity. Defining a covariant equals method for an enumeration
+value is exceptionally bad practice, since it would likely result
+in having two different enumeration values that compare as equals using
+the covariant enum method, and as not equal when compared normally.
+Don't do it.
+</p>
+
+    
+<h3><a name="EQ_OTHER_NO_OBJECT">Eq: equals() method defined that doesn't override equals(Object) (EQ_OTHER_NO_OBJECT)</a></h3>
+
+
+  <p> This class defines an <code>equals()</code>
+  method, that doesn't override the normal <code>equals(Object)</code> method
+  defined in the base <code>java.lang.Object</code> class.&nbsp; Instead, it
+  inherits an <code>equals(Object)</code> method from a superclass.
+  The class should probably define a <code>boolean equals(Object)</code> method.
+  </p>
+
+    
+<h3><a name="EQ_OTHER_USE_OBJECT">Eq: equals() method defined that doesn't override Object.equals(Object) (EQ_OTHER_USE_OBJECT)</a></h3>
+
+
+  <p> This class defines an <code>equals()</code>
+  method, that doesn't override the normal <code>equals(Object)</code> method
+  defined in the base <code>java.lang.Object</code> class.&nbsp;
+  The class should probably define a <code>boolean equals(Object)</code> method.
+  </p>
+
+    
+<h3><a name="EQ_OVERRIDING_EQUALS_NOT_SYMMETRIC">Eq: equals method overrides equals in superclass and may not be symmetric (EQ_OVERRIDING_EQUALS_NOT_SYMMETRIC)</a></h3>
+
+
+  <p> This class defines an equals method that overrides an equals method in a superclass. Both equals methods
+methods use <code>instanceof</code> in the determination of whether two objects are equal. This is fraught with peril,
+since it is important that the equals method is symmetrical (in other words, <code>a.equals(b) == b.equals(a)</code>).
+If B is a subtype of A, and A's equals method checks that the argument is an instanceof A, and B's equals method
+checks that the argument is an instanceof B, it is quite likely that the equivalence relation defined by these
+methods is not symmetric.
+</p>
+
+    
+<h3><a name="EQ_SELF_USE_OBJECT">Eq: Covariant equals() method defined, Object.equals(Object) inherited (EQ_SELF_USE_OBJECT)</a></h3>
+
+
+  <p> This class defines a covariant version of the <code>equals()</code>
+  method, but inherits the normal <code>equals(Object)</code> method
+  defined in the base <code>java.lang.Object</code> class.&nbsp;
+  The class should probably define a <code>boolean equals(Object)</code> method.
+  </p>
+
+    
+<h3><a name="FE_TEST_IF_EQUAL_TO_NOT_A_NUMBER">FE: Doomed test for equality to NaN (FE_TEST_IF_EQUAL_TO_NOT_A_NUMBER)</a></h3>
+
+   
+    <p>
+    This code checks to see if a floating point value is equal to the special
+    Not A Number value (e.g., <code>if (x == Double.NaN)</code>). However,
+    because of the special semantics of <code>NaN</code>, no value
+    is equal to <code>Nan</code>, including <code>NaN</code>. Thus,
+    <code>x == Double.NaN</code> always evaluates to false.
+
+    To check to see if a value contained in <code>x</code>
+    is the special Not A Number value, use
+    <code>Double.isNaN(x)</code> (or <code>Float.isNaN(x)</code> if
+    <code>x</code> is floating point precision).
+    </p>
+    
+     
+<h3><a name="VA_FORMAT_STRING_BAD_ARGUMENT">FS: Format string placeholder incompatible with passed argument (VA_FORMAT_STRING_BAD_ARGUMENT)</a></h3>
+
+
+<p>
+The format string placeholder is incompatible with the corresponding
+argument. For example,
+<code>
+  System.out.println("%d\n", "hello");
+</code>
+<p>The %d placeholder requires a numeric argument, but a string value is
+passed instead.
+A runtime exception will occur when
+this statement is executed.
+</p>
+
+     
+<h3><a name="VA_FORMAT_STRING_BAD_CONVERSION">FS: The type of a supplied argument doesn't match format specifier (VA_FORMAT_STRING_BAD_CONVERSION)</a></h3>
+
+
+<p>
+One of the arguments is uncompatible with the corresponding format string specifier.
+As a result, this will generate a runtime exception when executed.
+For example, <code>String.format("%d", "1")</code> will generate an exception, since
+the String "1" is incompatible with the format specifier %d.
+</p>
+
+     
+<h3><a name="VA_FORMAT_STRING_EXPECTED_MESSAGE_FORMAT_SUPPLIED">FS: MessageFormat supplied where printf style format expected (VA_FORMAT_STRING_EXPECTED_MESSAGE_FORMAT_SUPPLIED)</a></h3>
+
+
+<p>
+A method is called that expects a Java printf format string and a list of arguments.
+However, the format string doesn't contain any format specifiers (e.g., %s) but
+does contain message format elements (e.g., {0}).  It is likely
+that the code is supplying a MessageFormat string when a printf-style format string
+is required. At runtime, all of the arguments will be ignored
+and the format string will be returned exactly as provided without any formatting.
+</p>
+</p>
+
+     
+<h3><a name="VA_FORMAT_STRING_EXTRA_ARGUMENTS_PASSED">FS: More arguments are passed than are actually used in the format string (VA_FORMAT_STRING_EXTRA_ARGUMENTS_PASSED)</a></h3>
+
+
+<p>
+A format-string method with a variable number of arguments is called,
+but more arguments are passed than are actually used by the format string.
+This won't cause a runtime exception, but the code may be silently omitting
+information that was intended to be included in the formatted string.
+</p>
+
+     
+<h3><a name="VA_FORMAT_STRING_ILLEGAL">FS: Illegal format string (VA_FORMAT_STRING_ILLEGAL)</a></h3>
+
+
+<p>
+The format string is syntactically invalid,
+and a runtime exception will occur when
+this statement is executed.
+</p>
+
+     
+<h3><a name="VA_FORMAT_STRING_MISSING_ARGUMENT">FS: Format string references missing argument (VA_FORMAT_STRING_MISSING_ARGUMENT)</a></h3>
+
+
+<p>
+Not enough arguments are passed to satisfy a placeholder in the format string.
+A runtime exception will occur when
+this statement is executed.
+</p>
+
+     
+<h3><a name="VA_FORMAT_STRING_NO_PREVIOUS_ARGUMENT">FS: No previous argument for format string (VA_FORMAT_STRING_NO_PREVIOUS_ARGUMENT)</a></h3>
+
+
+<p>
+The format string specifies a relative index to request that the argument for the previous format specifier
+be reused. However, there is no previous argument.
+For example,
+</p>
+<p><code>formatter.format("%&lt;s %s", "a", "b")</code>
+</p>
+<p>would throw a MissingFormatArgumentException when executed.
+</p>
+
+     
+<h3><a name="GC_UNRELATED_TYPES">GC: No relationship between generic parameter and method argument (GC_UNRELATED_TYPES)</a></h3>
+
+     
+     <p> This call to a generic collection method contains an argument
+     with an incompatible class from that of the collection's parameter
+    (i.e., the type of the argument is neither a supertype nor a subtype
+        of the corresponding generic type argument).
+     Therefore, it is unlikely that the collection contains any objects
+    that are equal to the method argument used here.
+    Most likely, the wrong value is being passed to the method.</p>
+    <p>In general, instances of two unrelated classes are not equal.
+    For example, if the <code>Foo</code> and <code>Bar</code> classes
+    are not related by subtyping, then an instance of <code>Foo</code>
+        should not be equal to an instance of <code>Bar</code>.
+    Among other issues, doing so will likely result in an equals method
+    that is not symmetrical. For example, if you define the <code>Foo</code> class
+    so that a <code>Foo</code> can be equal to a <code>String</code>,
+    your equals method isn't symmetrical since a <code>String</code> can only be equal
+    to a <code>String</code>.
+    </p>
+    <p>In rare cases, people do define nonsymmetrical equals methods and still manage to make
+    their code work. Although none of the APIs document or guarantee it, it is typically
+    the case that if you check if a <code>Collection&lt;String&gt;</code> contains
+    a <code>Foo</code>, the equals method of argument (e.g., the equals method of the
+    <code>Foo</code> class) used to perform the equality checks.
+    </p>
+     
+    
+<h3><a name="HE_SIGNATURE_DECLARES_HASHING_OF_UNHASHABLE_CLASS">HE: Signature declares use of unhashable class in hashed construct (HE_SIGNATURE_DECLARES_HASHING_OF_UNHASHABLE_CLASS)</a></h3>
+
+
+  <p> A method, field or class declares a generic signature where a non-hashable class
+is used in context where a hashable class is required.
+A class that declares an equals method but inherits a hashCode() method
+from Object is unhashable, since it doesn't fulfill the requirement that
+equal objects have equal hashCodes.
+</p>
+
+    
+<h3><a name="HE_USE_OF_UNHASHABLE_CLASS">HE: Use of class without a hashCode() method in a hashed data structure (HE_USE_OF_UNHASHABLE_CLASS)</a></h3>
+
+
+  <p> A class defines an equals(Object)  method but not a hashCode() method,
+and thus doesn't fulfill the requirement that equal objects have equal hashCodes.
+An instance of this class is used in a hash data structure, making the need to
+fix this problem of highest importance.
+
+    
+<h3><a name="ICAST_INT_2_LONG_AS_INSTANT">ICAST: int value converted to long and used as absolute time (ICAST_INT_2_LONG_AS_INSTANT)</a></h3>
+
+
+<p>
+This code converts a 32-bit int value to a 64-bit long value, and then
+passes that value for a method parameter that requires an absolute time value.
+An absolute time value is the number
+of milliseconds since the standard base time known as "the epoch", namely January 1, 1970, 00:00:00 GMT.
+For example, the following method, intended to convert seconds since the epoc into a Date, is badly
+broken:</p>
+<pre>
+Date getDate(int seconds) { return new Date(seconds * 1000); }
+</pre>
+<p>The multiplication is done using 32-bit arithmetic, and then converted to a 64-bit value.
+When a 32-bit value is converted to 64-bits and used to express an absolute time
+value, only dates in December 1969 and January 1970 can be represented.</p>
+
+<p>Correct implementations for the above method are:</p>
+
+<pre>
+// Fails for dates after 2037
+Date getDate(int seconds) { return new Date(seconds * 1000L); }
+
+// better, works for all dates
+Date getDate(long seconds) { return new Date(seconds * 1000); }
+</pre>
+
+    
+<h3><a name="ICAST_INT_CAST_TO_DOUBLE_PASSED_TO_CEIL">ICAST: integral value cast to double and then passed to Math.ceil (ICAST_INT_CAST_TO_DOUBLE_PASSED_TO_CEIL)</a></h3>
+
+
+<p>
+This code converts an integral value (e.g., int or long)
+to a double precision
+floating point number and then
+passing the result to the Math.ceil() function, which rounds a double to
+the next higher integer value. This operation should always be a no-op,
+since the converting an integer to a double should give a number with no fractional part.
+It is likely that the operation that generated the value to be passed
+to Math.ceil was intended to be performed using double precision
+floating point arithmetic.
+</p>
+
+
+    
+<h3><a name="ICAST_INT_CAST_TO_FLOAT_PASSED_TO_ROUND">ICAST: int value cast to float and then passed to Math.round (ICAST_INT_CAST_TO_FLOAT_PASSED_TO_ROUND)</a></h3>
+
+
+<p>
+This code converts an int value to a float precision
+floating point number and then
+passing the result to the Math.round() function, which returns the int/long closest
+to the argument. This operation should always be a no-op,
+since the converting an integer to a float should give a number with no fractional part.
+It is likely that the operation that generated the value to be passed
+to Math.round was intended to be performed using
+floating point arithmetic.
+</p>
+
+
+    
+<h3><a name="IJU_ASSERT_METHOD_INVOKED_FROM_RUN_METHOD">IJU: JUnit assertion in run method will not be noticed by JUnit (IJU_ASSERT_METHOD_INVOKED_FROM_RUN_METHOD)</a></h3>
+
+
+<p> A JUnit assertion is performed in a run method. Failed JUnit assertions
+just result in exceptions being thrown.
+Thus, if this exception occurs in a thread other than the thread that invokes
+the test method, the exception will terminate the thread but not result
+in the test failing.
+</p>
+
+    
+<h3><a name="IJU_BAD_SUITE_METHOD">IJU: TestCase declares a bad suite method  (IJU_BAD_SUITE_METHOD)</a></h3>
+
+
+<p> Class is a JUnit TestCase and defines a suite() method.
+However, the suite method needs to be declared as either
+<pre>public static junit.framework.Test suite()</pre>
+or
+<pre>public static junit.framework.TestSuite suite()</pre>
+</p>
+
+    
+<h3><a name="IJU_NO_TESTS">IJU: TestCase has no tests (IJU_NO_TESTS)</a></h3>
+
+
+<p> Class is a JUnit TestCase but has not implemented any test methods</p>
+
+    
+<h3><a name="IJU_SETUP_NO_SUPER">IJU: TestCase defines setUp that doesn't call super.setUp() (IJU_SETUP_NO_SUPER)</a></h3>
+
+
+<p> Class is a JUnit TestCase and implements the setUp method. The setUp method should call
+super.setUp(), but doesn't.</p>
+
+    
+<h3><a name="IJU_SUITE_NOT_STATIC">IJU: TestCase implements a non-static suite method  (IJU_SUITE_NOT_STATIC)</a></h3>
+
+
+<p> Class is a JUnit TestCase and implements the suite() method.
+ The suite method should be declared as being static, but isn't.</p>
+
+    
+<h3><a name="IJU_TEARDOWN_NO_SUPER">IJU: TestCase defines tearDown that doesn't call super.tearDown() (IJU_TEARDOWN_NO_SUPER)</a></h3>
+
+
+<p> Class is a JUnit TestCase and implements the tearDown method. The tearDown method should call
+super.tearDown(), but doesn't.</p>
+
+    
+<h3><a name="IL_CONTAINER_ADDED_TO_ITSELF">IL: A collection is added to itself (IL_CONTAINER_ADDED_TO_ITSELF)</a></h3>
+
+
+<p>A collection is added to itself. As a result, computing the hashCode of this
+set will throw a StackOverflowException.
+</p>
+
+    
+<h3><a name="IL_INFINITE_LOOP">IL: An apparent infinite loop (IL_INFINITE_LOOP)</a></h3>
+
+
+<p>This loop doesn't seem to have a way to terminate (other than by perhaps
+throwing an exception).</p>
+
+    
+<h3><a name="IL_INFINITE_RECURSIVE_LOOP">IL: An apparent infinite recursive loop (IL_INFINITE_RECURSIVE_LOOP)</a></h3>
+
+
+<p>This method unconditionally invokes itself. This would seem to indicate
+an infinite recursive loop that will result in a stack overflow.</p>
+
+    
+<h3><a name="IM_MULTIPLYING_RESULT_OF_IREM">IM: Integer multiply of result of integer remainder (IM_MULTIPLYING_RESULT_OF_IREM)</a></h3>
+
+
+<p>
+The code multiplies the result of an integer remaining by an integer constant.
+Be sure you don't have your operator precedence confused. For example
+i % 60 * 1000 is (i % 60) * 1000, not i % (60 * 1000).
+</p>
+
+    
+<h3><a name="INT_BAD_COMPARISON_WITH_INT_VALUE">INT: Bad comparison of int value with long constant (INT_BAD_COMPARISON_WITH_INT_VALUE)</a></h3>
+
+
+<p> This code compares an int value with a long constant that is outside
+the range of values that can be represented as an int value.
+This comparison is vacuous and possibily to be incorrect.
+</p>
+
+    
+<h3><a name="INT_BAD_COMPARISON_WITH_NONNEGATIVE_VALUE">INT: Bad comparison of nonnegative value with negative constant (INT_BAD_COMPARISON_WITH_NONNEGATIVE_VALUE)</a></h3>
+
+
+<p> This code compares a value that is guaranteed to be non-negative with a negative constant.
+</p>
+
+    
+<h3><a name="INT_BAD_COMPARISON_WITH_SIGNED_BYTE">INT: Bad comparison of signed byte (INT_BAD_COMPARISON_WITH_SIGNED_BYTE)</a></h3>
+
+
+<p> Signed bytes can only have a value in the range -128 to 127. Comparing
+a signed byte with a value outside that range is vacuous and likely to be incorrect.
+To convert a signed byte <code>b</code> to an unsigned value in the range 0..255,
+use <code>0xff &amp; b</code>
+</p>
+
+    
+<h3><a name="IO_APPENDING_TO_OBJECT_OUTPUT_STREAM">IO: Doomed attempt to append to an object output stream (IO_APPENDING_TO_OBJECT_OUTPUT_STREAM)</a></h3>
+
+      
+      <p>
+     This code opens a file in append mode and then wraps the result in an object output stream.
+     This won't allow you to append to an existing object output stream stored in a file. If you want to be
+     able to append to an object output stream, you need to keep the object output stream open.
+      </p>
+      <p>The only situation in which opening a file in append mode and the writing an object output stream
+      could work is if on reading the file you plan to open it in random access mode and seek to the byte offset
+      where the append started.
+      </p>
+
+      <p>
+      TODO: example.
+      </p>
+      
+    
+<h3><a name="IP_PARAMETER_IS_DEAD_BUT_OVERWRITTEN">IP: A parameter is dead upon entry to a method but overwritten (IP_PARAMETER_IS_DEAD_BUT_OVERWRITTEN)</a></h3>
+
+
+<p>
+The initial value of this parameter is ignored, and the parameter
+is overwritten here. This often indicates a mistaken belief that
+the write to the parameter will be conveyed back to
+the caller.
+</p>
+
+    
+<h3><a name="MF_CLASS_MASKS_FIELD">MF: Class defines field that masks a superclass field (MF_CLASS_MASKS_FIELD)</a></h3>
+
+
+<p> This class defines a field with the same name as a visible
+instance field in a superclass.  This is confusing, and
+may indicate an error if methods update or access one of
+the fields when they wanted the other.</p>
+
+    
+<h3><a name="MF_METHOD_MASKS_FIELD">MF: Method defines a variable that obscures a field (MF_METHOD_MASKS_FIELD)</a></h3>
+
+
+<p> This method defines a local variable with the same name as a field
+in this class or a superclass.  This may cause the method to
+read an uninitialized value from the field, leave the field uninitialized,
+or both.</p>
+
+    
+<h3><a name="NP_ALWAYS_NULL">NP: Null pointer dereference (NP_ALWAYS_NULL)</a></h3>
+
+
+<p> A null pointer is dereferenced here.&nbsp; This will lead to a
+<code>NullPointerException</code> when the code is executed.</p>
+
+    
+<h3><a name="NP_ALWAYS_NULL_EXCEPTION">NP: Null pointer dereference in method on exception path (NP_ALWAYS_NULL_EXCEPTION)</a></h3>
+
+
+<p> A pointer which is null on an exception path is dereferenced here.&nbsp;
+This will lead to a <code>NullPointerException</code> when the code is executed.&nbsp;
+Note that because FindBugs currently does not prune infeasible exception paths,
+this may be a false warning.</p>
+
+<p> Also note that FindBugs considers the default case of a switch statement to
+be an exception path, since the default case is often infeasible.</p>
+
+    
+<h3><a name="NP_ARGUMENT_MIGHT_BE_NULL">NP: Method does not check for null argument (NP_ARGUMENT_MIGHT_BE_NULL)</a></h3>
+
+      
+      <p>
+    A parameter to this method has been identified as a value that should
+    always be checked to see whether or not it is null, but it is being dereferenced
+    without a preceding null check.
+      </p>
+      
+   
+<h3><a name="NP_CLOSING_NULL">NP: close() invoked on a value that is always null (NP_CLOSING_NULL)</a></h3>
+
+
+<p> close() is being invoked on a value that is always null. If this statement is executed,
+a null pointer exception will occur. But the big risk here you never close
+something that should be closed.
+
+    
+<h3><a name="NP_GUARANTEED_DEREF">NP: Null value is guaranteed to be dereferenced (NP_GUARANTEED_DEREF)</a></h3>
+
+          
+              <p>
+              There is a statement or branch that if executed guarantees that
+              a value is null at this point, and that
+              value that is guaranteed to be dereferenced
+              (except on forward paths involving runtime exceptions).
+              </p>
+        <p>Note that a check such as
+            <code>if (x == null) throw new NullPointerException();</code
+            is treated as a dereference of <code>x</code>.
+          
+      
+<h3><a name="NP_GUARANTEED_DEREF_ON_EXCEPTION_PATH">NP: Value is null and guaranteed to be dereferenced on exception path (NP_GUARANTEED_DEREF_ON_EXCEPTION_PATH)</a></h3>
+
+          
+              <p>
+              There is a statement or branch on an exception path
+                that if executed guarantees that
+              a value is null at this point, and that
+              value that is guaranteed to be dereferenced
+              (except on forward paths involving runtime exceptions).
+              </p>
+          
+      
+<h3><a name="NP_NONNULL_FIELD_NOT_INITIALIZED_IN_CONSTRUCTOR">NP: Nonnull field is not initialized (NP_NONNULL_FIELD_NOT_INITIALIZED_IN_CONSTRUCTOR)</a></h3>
+
+       
+       <p> The field is marked as nonnull, but isn't written to by the constructor.
+    The field might be initialized elsewhere during constructor, or might always
+    be initialized before use.
+       </p>
+       
+       
+<h3><a name="NP_NONNULL_PARAM_VIOLATION">NP: Method call passes null to a nonnull parameter  (NP_NONNULL_PARAM_VIOLATION)</a></h3>
+
+      
+      <p>
+      This method passes a null value as the parameter of a method which
+    must be nonnull. Either this parameter has been explicitly marked
+    as @Nonnull, or analysis has determined that this parameter is
+    always dereferenced.
+      </p>
+      
+   
+<h3><a name="NP_NONNULL_RETURN_VIOLATION">NP: Method may return null, but is declared @NonNull (NP_NONNULL_RETURN_VIOLATION)</a></h3>
+
+      
+      <p>
+      This method may return a null value, but the method (or a superclass method
+      which it overrides) is declared to return @NonNull.
+      </p>
+      
+   
+<h3><a name="NP_NULL_INSTANCEOF">NP: A known null value is checked to see if it is an instance of a type (NP_NULL_INSTANCEOF)</a></h3>
+
+
+<p>
+This instanceof test will always return false, since the value being checked is guaranteed to be null.
+Although this is safe, make sure it isn't
+an indication of some misunderstanding or some other logic error.
+</p>
+
+    
+<h3><a name="NP_NULL_ON_SOME_PATH">NP: Possible null pointer dereference (NP_NULL_ON_SOME_PATH)</a></h3>
+
+
+<p> There is a branch of statement that, <em>if executed,</em>  guarantees that
+a null value will be dereferenced, which
+would generate a <code>NullPointerException</code> when the code is executed.
+Of course, the problem might be that the branch or statement is infeasible and that
+the null pointer exception can't ever be executed; deciding that is beyond the ability of FindBugs.
+</p>
+
+    
+<h3><a name="NP_NULL_ON_SOME_PATH_EXCEPTION">NP: Possible null pointer dereference in method on exception path (NP_NULL_ON_SOME_PATH_EXCEPTION)</a></h3>
+
+
+<p> A reference value which is null on some exception control path is
+dereferenced here.&nbsp; This may lead to a <code>NullPointerException</code>
+when the code is executed.&nbsp;
+Note that because FindBugs currently does not prune infeasible exception paths,
+this may be a false warning.</p>
+
+<p> Also note that FindBugs considers the default case of a switch statement to
+be an exception path, since the default case is often infeasible.</p>
+
+    
+<h3><a name="NP_NULL_PARAM_DEREF">NP: Method call passes null for nonnull parameter (NP_NULL_PARAM_DEREF)</a></h3>
+
+      
+      <p>
+      This method call passes a null value for a nonnull method parameter.
+    Either the parameter is annotated as a parameter that should
+    always be nonnull, or analysis has shown that it will always be
+    dereferenced.
+      </p>
+      
+   
+<h3><a name="NP_NULL_PARAM_DEREF_ALL_TARGETS_DANGEROUS">NP: Method call passes null for nonnull parameter (NP_NULL_PARAM_DEREF_ALL_TARGETS_DANGEROUS)</a></h3>
+
+      
+      <p>
+      A possibly-null value is passed at a call site where all known
+      target methods require the parameter to be nonnull.
+    Either the parameter is annotated as a parameter that should
+    always be nonnull, or analysis has shown that it will always be
+    dereferenced.
+      </p>
+      
+   
+<h3><a name="NP_NULL_PARAM_DEREF_NONVIRTUAL">NP: Non-virtual method call passes null for nonnull parameter (NP_NULL_PARAM_DEREF_NONVIRTUAL)</a></h3>
+
+      
+      <p>
+      A possibly-null value is passed to a nonnull method parameter.
+    Either the parameter is annotated as a parameter that should
+    always be nonnull, or analysis has shown that it will always be
+    dereferenced.
+      </p>
+      
+   
+<h3><a name="NP_STORE_INTO_NONNULL_FIELD">NP: Store of null value into field annotated NonNull (NP_STORE_INTO_NONNULL_FIELD)</a></h3>
+
+      
+<p> A value that could be null is stored into a field that has been annotated as NonNull. </p>
+
+    
+<h3><a name="NP_UNWRITTEN_FIELD">NP: Read of unwritten field (NP_UNWRITTEN_FIELD)</a></h3>
+
+
+  <p> The program is dereferencing a field that does not seem to ever have a non-null value written to it.
+Unless the field is initialized via some mechanism not seen by the analysis,
+dereferencing this value will generate a null pointer exception.
+</p>
+
+    
+<h3><a name="NM_BAD_EQUAL">Nm: Class defines equal(Object); should it be equals(Object)? (NM_BAD_EQUAL)</a></h3>
+
+
+<p> This class defines a method <code>equal(Object)</code>.&nbsp; This method does
+not override the <code>equals(Object)</code> method in <code>java.lang.Object</code>,
+which is probably what was intended.</p>
+
+    
+<h3><a name="NM_LCASE_HASHCODE">Nm: Class defines hashcode(); should it be hashCode()? (NM_LCASE_HASHCODE)</a></h3>
+
+
+  <p> This class defines a method called <code>hashcode()</code>.&nbsp; This method
+  does not override the <code>hashCode()</code> method in <code>java.lang.Object</code>,
+  which is probably what was intended.</p>
+
+    
+<h3><a name="NM_LCASE_TOSTRING">Nm: Class defines tostring(); should it be toString()? (NM_LCASE_TOSTRING)</a></h3>
+
+
+  <p> This class defines a method called <code>tostring()</code>.&nbsp; This method
+  does not override the <code>toString()</code> method in <code>java.lang.Object</code>,
+  which is probably what was intended.</p>
+
+    
+<h3><a name="NM_METHOD_CONSTRUCTOR_CONFUSION">Nm: Apparent method/constructor confusion (NM_METHOD_CONSTRUCTOR_CONFUSION)</a></h3>
+
+
+  <p> This regular method has the same name as the class it is defined in. It is likely that this was intended to be a constructor.
+      If it was intended to be a constructor, remove the declaration of a void return value.
+    If you had accidently defined this method, realized the mistake, defined a proper constructor
+    but can't get rid of this method due to backwards compatibility, deprecate the method.
+</p>
+
+    
+<h3><a name="NM_VERY_CONFUSING">Nm: Very confusing method names (NM_VERY_CONFUSING)</a></h3>
+
+
+  <p> The referenced methods have names that differ only by capitalization.
+This is very confusing because if the capitalization were
+identical then one of the methods would override the other.
+</p>
+
+    
+<h3><a name="NM_WRONG_PACKAGE">Nm: Method doesn't override method in superclass due to wrong package for parameter (NM_WRONG_PACKAGE)</a></h3>
+
+
+  <p> The method in the subclass doesn't override a similar method in a superclass because the type of a parameter doesn't exactly match
+the type of the corresponding parameter in the superclass. For example, if you have:</p>
+
+<blockquote>
+<pre>
+import alpha.Foo;
+public class A {
+  public int f(Foo x) { return 17; }
+}
+----
+import beta.Foo;
+public class B extends A {
+  public int f(Foo x) { return 42; }
+}
+</pre>
+</blockquote>
+
+<p>The <code>f(Foo)</code> method defined in class <code>B</code> doesn't
+override the
+<code>f(Foo)</code> method defined in class <code>A</code>, because the argument
+types are <code>Foo</code>'s from different packages.
+</p>
+
+    
+<h3><a name="QBA_QUESTIONABLE_BOOLEAN_ASSIGNMENT">QBA: Method assigns boolean literal in boolean expression (QBA_QUESTIONABLE_BOOLEAN_ASSIGNMENT)</a></h3>
+
+      
+      <p>
+      This method assigns a literal boolean value (true or false) to a boolean variable inside
+      an if or while expression. Most probably this was supposed to be a boolean comparison using
+      ==, not an assignment using =.
+      </p>
+      
+    
+<h3><a name="RC_REF_COMPARISON">RC: Suspicious reference comparison (RC_REF_COMPARISON)</a></h3>
+
+
+<p> This method compares two reference values using the == or != operator,
+where the correct way to compare instances of this type is generally
+with the equals() method.
+It is possible to create distinct instances that are equal but do not compare as == since
+they are different objects.
+Examples of classes which should generally
+not be compared by reference are java.lang.Integer, java.lang.Float, etc.</p>
+
+    
+<h3><a name="RCN_REDUNDANT_NULLCHECK_WOULD_HAVE_BEEN_A_NPE">RCN: Nullcheck of value previously dereferenced (RCN_REDUNDANT_NULLCHECK_WOULD_HAVE_BEEN_A_NPE)</a></h3>
+
+
+<p> A value is checked here to see whether it is null, but this value can't
+be null because it was previously dereferenced and if it were null a null pointer
+exception would have occurred at the earlier dereference.
+Essentially, this code and the previous dereference
+disagree as to whether this value is allowed to be null. Either the check is redundant
+or the previous dereference is erroneous.</p>
+
+    
+<h3><a name="RE_BAD_SYNTAX_FOR_REGULAR_EXPRESSION">RE: Invalid syntax for regular expression (RE_BAD_SYNTAX_FOR_REGULAR_EXPRESSION)</a></h3>
+
+
+<p>
+The code here uses a regular expression that is invalid according to the syntax
+for regular expressions. This statement will throw a PatternSyntaxException when
+executed.
+</p>
+
+    
+<h3><a name="RE_CANT_USE_FILE_SEPARATOR_AS_REGULAR_EXPRESSION">RE: File.separator used for regular expression (RE_CANT_USE_FILE_SEPARATOR_AS_REGULAR_EXPRESSION)</a></h3>
+
+
+<p>
+The code here uses <code>File.separator</code>
+where a regular expression is required. This will fail on Windows
+platforms, where the <code>File.separator</code> is a backslash, which is interpreted in a
+regular expression as an escape character. Amoung other options, you can just use
+<code>File.separatorChar=='\\' ? "\\\\" : File.separator</code> instead of
+<code>File.separator</code>
+
+</p>
+
+    
+<h3><a name="RE_POSSIBLE_UNINTENDED_PATTERN">RE: "." used for regular expression (RE_POSSIBLE_UNINTENDED_PATTERN)</a></h3>
+
+
+<p>
+A String function is being invoked and "." is being passed
+to a parameter that takes a regular expression as an argument. Is this what you intended?
+For example
+s.replaceAll(".", "/") will return a String in which <em>every</em>
+character has been replaced by a / character,
+and s.split(".") <em>always</em> returns a zero length array of String.
+</p>
+
+    
+<h3><a name="RV_01_TO_INT">RV: Random value from 0 to 1 is coerced to the integer 0 (RV_01_TO_INT)</a></h3>
+
+
+  <p>A random value from 0 to 1 is being coerced to the integer value 0. You probably
+want to multiple the random value by something else before coercing it to an integer, or use the <code>Random.nextInt(n)</code> method.
+</p>
+
+    
+<h3><a name="RV_ABSOLUTE_VALUE_OF_HASHCODE">RV: Bad attempt to compute absolute value of signed 32-bit hashcode  (RV_ABSOLUTE_VALUE_OF_HASHCODE)</a></h3>
+
+
+<p> This code generates a hashcode and then computes
+the absolute value of that hashcode.  If the hashcode
+is <code>Integer.MIN_VALUE</code>, then the result will be negative as well (since
+<code>Math.abs(Integer.MIN_VALUE) == Integer.MIN_VALUE</code>).
+</p>
+<p>One out of 2^32 strings have a hashCode of Integer.MIN_VALUE,
+including "polygenelubricants" "GydZG_" and ""DESIGNING WORKHOUSES".
+</p>
+
+    
+<h3><a name="RV_ABSOLUTE_VALUE_OF_RANDOM_INT">RV: Bad attempt to compute absolute value of signed random integer (RV_ABSOLUTE_VALUE_OF_RANDOM_INT)</a></h3>
+
+
+<p> This code generates a random signed integer and then computes
+the absolute value of that random integer.  If the number returned by the random number
+generator is <code>Integer.MIN_VALUE</code>, then the result will be negative as well (since
+<code>Math.abs(Integer.MIN_VALUE) == Integer.MIN_VALUE</code>). (Same problem arised for long values as well).
+</p>
+
+    
+<h3><a name="RV_CHECK_COMPARETO_FOR_SPECIFIC_RETURN_VALUE">RV: Code checks for specific values returned by compareTo (RV_CHECK_COMPARETO_FOR_SPECIFIC_RETURN_VALUE)</a></h3>
+
+
+   <p> This code invoked a compareTo or compare method, and checks to see if the return value is a specific value,
+such as 1 or -1. When invoking these methods, you should only check the sign of the result, not for any specific
+non-zero value. While many or most compareTo and compare methods only return -1, 0 or 1, some of them
+will return other values.
+
+    
+<h3><a name="RV_EXCEPTION_NOT_THROWN">RV: Exception created and dropped rather than thrown (RV_EXCEPTION_NOT_THROWN)</a></h3>
+
+
+   <p> This code creates an exception (or error) object, but doesn't do anything with it. For example,
+something like </p>
+<blockquote>
+<pre>
+if (x &lt; 0)
+  new IllegalArgumentException("x must be nonnegative");
+</pre>
+</blockquote>
+<p>It was probably the intent of the programmer to throw the created exception:</p>
+<blockquote>
+<pre>
+if (x &lt; 0)
+  throw new IllegalArgumentException("x must be nonnegative");
+</pre>
+</blockquote>
+
+    
+<h3><a name="RV_RETURN_VALUE_IGNORED">RV: Method ignores return value (RV_RETURN_VALUE_IGNORED)</a></h3>
+
+
+   <p> The return value of this method should be checked. One common
+cause of this warning is to invoke a method on an immutable object,
+thinking that it updates the object. For example, in the following code
+fragment,</p>
+<blockquote>
+<pre>
+String dateString = getHeaderField(name);
+dateString.trim();
+</pre>
+</blockquote>
+<p>the programmer seems to be thinking that the trim() method will update
+the String referenced by dateString. But since Strings are immutable, the trim()
+function returns a new String value, which is being ignored here. The code
+should be corrected to: </p>
+<blockquote>
+<pre>
+String dateString = getHeaderField(name);
+dateString = dateString.trim();
+</pre>
+</blockquote>
+
+    
+<h3><a name="RpC_REPEATED_CONDITIONAL_TEST">RpC: Repeated conditional tests (RpC_REPEATED_CONDITIONAL_TEST)</a></h3>
+
+
+<p>The code contains a conditional test is performed twice, one right after the other
+(e.g., <code>x == 0 || x == 0</code>). Perhaps the second occurrence is intended to be something else
+(e.g., <code>x == 0 || y == 0</code>).
+</p>
+
+    
+<h3><a name="SA_FIELD_SELF_ASSIGNMENT">SA: Self assignment of field (SA_FIELD_SELF_ASSIGNMENT)</a></h3>
+
+
+<p> This method contains a self assignment of a field; e.g.
+</p>
+<pre>
+  int x;
+  public void foo() {
+    x = x;
+  }
+</pre>
+<p>Such assignments are useless, and may indicate a logic error or typo.</p>
+
+    
+<h3><a name="SA_FIELD_SELF_COMPARISON">SA: Self comparison of field with itself (SA_FIELD_SELF_COMPARISON)</a></h3>
+
+
+<p> This method compares a field with itself, and may indicate a typo or
+a logic error.  Make sure that you are comparing the right things.
+</p>
+
+    
+<h3><a name="SA_FIELD_SELF_COMPUTATION">SA: Nonsensical self computation involving a field (e.g., x & x) (SA_FIELD_SELF_COMPUTATION)</a></h3>
+
+
+<p> This method performs a nonsensical computation of a field with another
+reference to the same field (e.g., x&x or x-x). Because of the nature
+of the computation, this operation doesn't seem to make sense,
+and may indicate a typo or
+a logic error.  Double check the computation.
+</p>
+
+    
+<h3><a name="SA_LOCAL_SELF_ASSIGNMENT_INSTEAD_OF_FIELD">SA: Self assignment of local rather than assignment to field (SA_LOCAL_SELF_ASSIGNMENT_INSTEAD_OF_FIELD)</a></h3>
+
+
+<p> This method contains a self assignment of a local variable, and there
+is a field with an identical name.
+assignment appears to have been ; e.g.</p>
+<pre>
+  int foo;
+  public void setFoo(int foo) {
+    foo = foo;
+  }
+</pre>
+<p>The assignment is useless. Did you mean to assign to the field instead?</p>
+
+    
+<h3><a name="SA_LOCAL_SELF_COMPARISON">SA: Self comparison of value with itself (SA_LOCAL_SELF_COMPARISON)</a></h3>
+
+
+<p> This method compares a local variable with itself, and may indicate a typo or
+a logic error.  Make sure that you are comparing the right things.
+</p>
+
+    
+<h3><a name="SA_LOCAL_SELF_COMPUTATION">SA: Nonsensical self computation involving a variable (e.g., x & x) (SA_LOCAL_SELF_COMPUTATION)</a></h3>
+
+
+<p> This method performs a nonsensical computation of a local variable with another
+reference to the same variable (e.g., x&x or x-x). Because of the nature
+of the computation, this operation doesn't seem to make sense,
+and may indicate a typo or
+a logic error.  Double check the computation.
+</p>
+
+    
+<h3><a name="SF_DEAD_STORE_DUE_TO_SWITCH_FALLTHROUGH">SF: Dead store due to switch statement fall through (SF_DEAD_STORE_DUE_TO_SWITCH_FALLTHROUGH)</a></h3>
+
+
+  <p> A value stored in the previous switch case is overwritten here due to a switch fall through. It is likely that
+    you forgot to put a break or return at the end of the previous case.
+</p>
+
+    
+<h3><a name="SF_DEAD_STORE_DUE_TO_SWITCH_FALLTHROUGH_TO_THROW">SF: Dead store due to switch statement fall through to throw (SF_DEAD_STORE_DUE_TO_SWITCH_FALLTHROUGH_TO_THROW)</a></h3>
+
+
+  <p> A value stored in the previous switch case is ignored here due to a switch fall through to a place where
+    an exception is thrown. It is likely that
+    you forgot to put a break or return at the end of the previous case.
+</p>
+
+    
+<h3><a name="SIC_THREADLOCAL_DEADLY_EMBRACE">SIC: Deadly embrace of non-static inner class and thread local (SIC_THREADLOCAL_DEADLY_EMBRACE)</a></h3>
+
+
+  <p> This class is an inner class, but should probably be a static inner class.
+  As it is, there is a serious danger of a deadly embrace between the inner class
+  and the thread local in the outer class. Because the inner class isn't static,
+  it retains a reference to the outer class.
+  If the thread local contains a reference to an instance of the inner
+  class, the inner and outer instance will both be reachable
+  and not eligible for garbage collection.
+</p>
+
+    
+<h3><a name="SIO_SUPERFLUOUS_INSTANCEOF">SIO: Unnecessary type check done using instanceof operator (SIO_SUPERFLUOUS_INSTANCEOF)</a></h3>
+
+
+<p> Type check performed using the instanceof operator where it can be statically determined whether the object
+is of the type requested. </p>
+
+    
+<h3><a name="SQL_BAD_PREPARED_STATEMENT_ACCESS">SQL: Method attempts to access a prepared statement parameter with index 0 (SQL_BAD_PREPARED_STATEMENT_ACCESS)</a></h3>
+
+
+<p> A call to a setXXX method of a prepared statement was made where the
+parameter index is 0. As parameter indexes start at index 1, this is always a mistake.</p>
+
+    
+<h3><a name="SQL_BAD_RESULTSET_ACCESS">SQL: Method attempts to access a result set field with index 0 (SQL_BAD_RESULTSET_ACCESS)</a></h3>
+
+
+<p> A call to getXXX or updateXXX methods of a result set was made where the
+field index is 0. As ResultSet fields start at index 1, this is always a mistake.</p>
+
+    
+<h3><a name="STI_INTERRUPTED_ON_CURRENTTHREAD">STI: Unneeded use of currentThread() call, to call interrupted()  (STI_INTERRUPTED_ON_CURRENTTHREAD)</a></h3>
+
+
+<p>
+This method invokes the Thread.currentThread() call, just to call the interrupted() method. As interrupted() is a
+static method, is more simple and clear to use Thread.interrupted().
+</p>
+
+    
+<h3><a name="STI_INTERRUPTED_ON_UNKNOWNTHREAD">STI: Static Thread.interrupted() method invoked on thread instance (STI_INTERRUPTED_ON_UNKNOWNTHREAD)</a></h3>
+
+
+<p>
+This method invokes the Thread.interrupted() method on a Thread object that appears to be a Thread object that is
+not the current thread. As the interrupted() method is static, the interrupted method will be called on a different
+object than the one the author intended.
+</p>
+
+    
+<h3><a name="SE_METHOD_MUST_BE_PRIVATE">Se: Method must be private in order for serialization to work (SE_METHOD_MUST_BE_PRIVATE)</a></h3>
+
+
+  <p> This class implements the <code>Serializable</code> interface, and defines a method
+  for custom serialization/deserialization. But since that method isn't declared private,
+  it will be silently ignored by the serialization/deserialization API.</p>
+
+    
+<h3><a name="SE_READ_RESOLVE_IS_STATIC">Se: The readResolve method must not be declared as a static method.   (SE_READ_RESOLVE_IS_STATIC)</a></h3>
+
+
+  <p> In order for the readResolve method to be recognized by the serialization
+mechanism, it must not be declared as a static method.
+</p>
+
+    
+<h3><a name="TQ_ALWAYS_VALUE_USED_WHERE_NEVER_REQUIRED">TQ: Value annotated as carrying a type qualifier used where a value that must not carry that qualifier is required (TQ_ALWAYS_VALUE_USED_WHERE_NEVER_REQUIRED)</a></h3>
+
+      
+        <p>
+        A value specified as carrying a type qualifier annotation is
+        consumed in a location or locations requiring that the value not
+        carry that annotation.
+        </p>
+
+        <p>
+        More precisely, a value annotated with a type qualifier specifying when=ALWAYS
+        is guaranteed to reach a use or uses where the same type qualifier specifies when=NEVER.
+        </p>
+
+        <p>
+        For example, say that @NonNegative is a nickname for
+        the type qualifier annotation @Negative(when=When.NEVER).
+        The following code will generate this warning because
+        the return statement requires a @NonNegative value,
+        but receives one that is marked as @Negative.
+        </p>
+        <blockquote>
+<pre>
+public @NonNegative Integer example(@Negative Integer value) {
+    return value;
+}
+</pre>
+        </blockquote>
+      
+    
+<h3><a name="TQ_COMPARING_VALUES_WITH_INCOMPATIBLE_TYPE_QUALIFIERS">TQ: Comparing values with incompatible type qualifiers (TQ_COMPARING_VALUES_WITH_INCOMPATIBLE_TYPE_QUALIFIERS)</a></h3>
+
+      
+        <p>
+        A value specified as carrying a type qualifier annotation is
+        compared with a value that doesn't ever carry that qualifier.
+        </p>
+
+        <p>
+        More precisely, a value annotated with a type qualifier specifying when=ALWAYS
+        is compared with a value that where the same type qualifier specifies when=NEVER.
+        </p>
+
+        <p>
+        For example, say that @NonNegative is a nickname for
+        the type qualifier annotation @Negative(when=When.NEVER).
+        The following code will generate this warning because
+        the return statement requires a @NonNegative value,
+        but receives one that is marked as @Negative.
+        </p>
+        <blockquote>
+<pre>
+public boolean example(@Negative Integer value1, @NonNegative Integer value2) {
+    return value1.equals(value2);
+}
+</pre>
+        </blockquote>
+      
+    
+<h3><a name="TQ_MAYBE_SOURCE_VALUE_REACHES_ALWAYS_SINK">TQ: Value that might not carry a type qualifier is always used in a way requires that type qualifier (TQ_MAYBE_SOURCE_VALUE_REACHES_ALWAYS_SINK)</a></h3>
+
+      
+      <p>
+      A value that is annotated as possibility not being an instance of
+    the values denoted by the type qualifier, and the value is guaranteed to be used
+    in a way that requires values denoted by that type qualifier.
+      </p>
+      
+    
+<h3><a name="TQ_MAYBE_SOURCE_VALUE_REACHES_NEVER_SINK">TQ: Value that might carry a type qualifier is always used in a way prohibits it from having that type qualifier (TQ_MAYBE_SOURCE_VALUE_REACHES_NEVER_SINK)</a></h3>
+
+      
+      <p>
+      A value that is annotated as possibility being an instance of
+    the values denoted by the type qualifier, and the value is guaranteed to be used
+    in a way that prohibits values denoted by that type qualifier.
+      </p>
+      
+    
+<h3><a name="TQ_NEVER_VALUE_USED_WHERE_ALWAYS_REQUIRED">TQ: Value annotated as never carrying a type qualifier used where value carrying that qualifier is required (TQ_NEVER_VALUE_USED_WHERE_ALWAYS_REQUIRED)</a></h3>
+
+      
+        <p>
+        A value specified as not carrying a type qualifier annotation is guaranteed
+        to be consumed in a location or locations requiring that the value does
+        carry that annotation.
+        </p>
+
+        <p>
+        More precisely, a value annotated with a type qualifier specifying when=NEVER
+        is guaranteed to reach a use or uses where the same type qualifier specifies when=ALWAYS.
+        </p>
+
+        <p>
+        TODO: example
+        </p>
+      
+    
+<h3><a name="UMAC_UNCALLABLE_METHOD_OF_ANONYMOUS_CLASS">UMAC: Uncallable method defined in anonymous class (UMAC_UNCALLABLE_METHOD_OF_ANONYMOUS_CLASS)</a></h3>
+
+
+<p> This anonymous class defined a method that is not directly invoked and does not override
+a method in a superclass. Since methods in other classes cannot directly invoke methods
+declared in an anonymous class, it seems that this method is uncallable. The method
+might simply be dead code, but it is also possible that the method is intended to
+override a method declared in a superclass, and due to an typo or other error the method does not,
+in fact, override the method it is intended to.
+</p>
+
+
+<h3><a name="UR_UNINIT_READ">UR: Uninitialized read of field in constructor (UR_UNINIT_READ)</a></h3>
+
+
+  <p> This constructor reads a field which has not yet been assigned a value.&nbsp;
+  This is often caused when the programmer mistakenly uses the field instead
+  of one of the constructor's parameters.</p>
+
+    
+<h3><a name="UR_UNINIT_READ_CALLED_FROM_SUPER_CONSTRUCTOR">UR: Uninitialized read of field method called from constructor of superclass (UR_UNINIT_READ_CALLED_FROM_SUPER_CONSTRUCTOR)</a></h3>
+
+
+  <p> This method is invoked in the constructor of of the superclass. At this point,
+    the fields of the class have not yet initialized.</p>
+<p>To make this more concrete, consider the following classes:</p>
+<pre>abstract class A {
+  int hashCode;
+  abstract Object getValue();
+  A() {
+    hashCode = getValue().hashCode();
+    }
+  }
+class B extends A {
+  Object value;
+  B(Object v) {
+    this.value = v;
+    }
+  Object getValue() {
+    return value;
+  }
+  }</pre>
+<p>When a <code>B</code> is constructed,
+the constructor for the <code>A</code> class is invoked
+<em>before</em> the constructor for <code>B</code> sets <code>value</code>.
+Thus, when the constructor for <code>A</code> invokes <code>getValue</code>,
+an uninitialized value is read for <code>value</code>
+</p>
+
+    
+<h3><a name="DMI_INVOKING_TOSTRING_ON_ANONYMOUS_ARRAY">USELESS_STRING: Invocation of toString on an array (DMI_INVOKING_TOSTRING_ON_ANONYMOUS_ARRAY)</a></h3>
+
+
+<p>
+The code invokes toString on an (anonymous) array.  Calling toString on an array generates a fairly useless result
+such as [C@16f0472. Consider using Arrays.toString to convert the array into a readable
+String that gives the contents of the array. See Programming Puzzlers, chapter 3, puzzle 12.
+</p>
+
+    
+<h3><a name="DMI_INVOKING_TOSTRING_ON_ARRAY">USELESS_STRING: Invocation of toString on an array (DMI_INVOKING_TOSTRING_ON_ARRAY)</a></h3>
+
+
+<p>
+The code invokes toString on an array, which will generate a fairly useless result
+such as [C@16f0472. Consider using Arrays.toString to convert the array into a readable
+String that gives the contents of the array. See Programming Puzzlers, chapter 3, puzzle 12.
+</p>
+
+    
+<h3><a name="VA_FORMAT_STRING_BAD_CONVERSION_FROM_ARRAY">USELESS_STRING: Array formatted in useless way using format string (VA_FORMAT_STRING_BAD_CONVERSION_FROM_ARRAY)</a></h3>
+
+
+<p>
+One of the arguments being formatted with a format string is an array. This will be formatted
+using a fairly useless format, such as [I@304282, which doesn't actually show the contents
+of the array.
+Consider wrapping the array using <code>Arrays.asList(...)</code> before handling it off to a formatted.
+</p>
+
+     
+<h3><a name="UWF_NULL_FIELD">UwF: Field only ever set to null (UWF_NULL_FIELD)</a></h3>
+
+
+  <p> All writes to this field are of the constant value null, and thus
+all reads of the field will return null.
+Check for errors, or remove it if it is useless.</p>
+
+    
+<h3><a name="UWF_UNWRITTEN_FIELD">UwF: Unwritten field (UWF_UNWRITTEN_FIELD)</a></h3>
+
+
+  <p> This field is never written.&nbsp; All reads of it will return the default
+value. Check for errors (should it have been initialized?), or remove it if it is useless.</p>
+
+    
+<h3><a name="VA_PRIMITIVE_ARRAY_PASSED_TO_OBJECT_VARARG">VA: Primitive array passed to function expecting a variable number of object arguments (VA_PRIMITIVE_ARRAY_PASSED_TO_OBJECT_VARARG)</a></h3>
+
+
+<p>
+This code passes a primitive array to a function that takes a variable number of object arguments.
+This creates an array of length one to hold the primitive array and passes it to the function.
+</p>
+
+    
+<h3><a name="LG_LOST_LOGGER_DUE_TO_WEAK_REFERENCE">LG: Potential lost logger changes due to weak reference in OpenJDK (LG_LOST_LOGGER_DUE_TO_WEAK_REFERENCE)</a></h3>
+
+          
+<p>OpenJDK introduces a potential incompatibility.
+ In particular, the java.util.logging.Logger behavior has
+  changed. Instead of using strong references, it now uses weak references
+  internally. That's a reasonable change, but unfortunately some code relies on
+  the old behavior - when changing logger configuration, it simply drops the
+  logger reference. That means that the garbage collector is free to reclaim
+  that memory, which means that the logger configuration is lost. For example,
+consider:
+</p>
+
+<p><pre>public static void initLogging() throws Exception {
+ Logger logger = Logger.getLogger("edu.umd.cs");
+ logger.addHandler(new FileHandler()); // call to change logger configuration
+ logger.setUseParentHandlers(false); // another call to change logger configuration
+}</pre></p>
+
+<p>The logger reference is lost at the end of the method (it doesn't
+escape the method), so if you have a garbage collection cycle just
+after the call to initLogging, the logger configuration is lost
+(because Logger only keeps weak references).</p>
+
+<p><pre>public static void main(String[] args) throws Exception {
+ initLogging(); // adds a file handler to the logger
+ System.gc(); // logger configuration lost
+ Logger.getLogger("edu.umd.cs").info("Some message"); // this isn't logged to the file as expected
+}</pre></p>
+<p><em>Ulf Ochsenfahrt and Eric Fellheimer</em></p>
+          
+      
+<h3><a name="OBL_UNSATISFIED_OBLIGATION">OBL: Method may fail to clean up stream or resource (OBL_UNSATISFIED_OBLIGATION)</a></h3>
+
+          
+          <p>
+          This method may fail to clean up (close, dispose of) a stream,
+          database object, or other
+          resource requiring an explicit cleanup operation.
+          </p>
+
+          <p>
+          In general, if a method opens a stream or other resource,
+          the method should use a try/finally block to ensure that
+          the stream or resource is cleaned up before the method
+          returns.
+          </p>
+
+          <p>
+          This bug pattern is essentially the same as the
+          OS_OPEN_STREAM and ODR_OPEN_DATABASE_RESOURCE
+          bug patterns, but is based on a different
+          (and hopefully better) static analysis technique.
+          We are interested is getting feedback about the
+          usefulness of this bug pattern.
+          To send feedback, either:
+          </p>
+          <ul>
+            <li>send email to findbugs@cs.umd.edu</li>
+            <li>file a bug report: <a href="http://findbugs.sourceforge.net/reportingBugs.html">http://findbugs.sourceforge.net/reportingBugs.html</a></li>
+          </ul>
+
+          <p>
+          In particular,
+          the false-positive suppression heuristics for this
+          bug pattern have not been extensively tuned, so
+          reports about false positives are helpful to us.
+          </p>
+
+          <p>
+          See Weimer and Necula, <i>Finding and Preventing Run-Time Error Handling Mistakes</i>, for
+          a description of the analysis technique.
+          </p>
+          
+      
+<h3><a name="OBL_UNSATISFIED_OBLIGATION_EXCEPTION_EDGE">OBL: Method may fail to clean up stream or resource on checked exception (OBL_UNSATISFIED_OBLIGATION_EXCEPTION_EDGE)</a></h3>
+
+          
+          <p>
+          This method may fail to clean up (close, dispose of) a stream,
+          database object, or other
+          resource requiring an explicit cleanup operation.
+          </p>
+
+          <p>
+          In general, if a method opens a stream or other resource,
+          the method should use a try/finally block to ensure that
+          the stream or resource is cleaned up before the method
+          returns.
+          </p>
+
+          <p>
+          This bug pattern is essentially the same as the
+          OS_OPEN_STREAM and ODR_OPEN_DATABASE_RESOURCE
+          bug patterns, but is based on a different
+          (and hopefully better) static analysis technique.
+          We are interested is getting feedback about the
+          usefulness of this bug pattern.
+          To send feedback, either:
+          </p>
+          <ul>
+            <li>send email to findbugs@cs.umd.edu</li>
+            <li>file a bug report: <a href="http://findbugs.sourceforge.net/reportingBugs.html">http://findbugs.sourceforge.net/reportingBugs.html</a></li>
+          </ul>
+
+          <p>
+          In particular,
+          the false-positive suppression heuristics for this
+          bug pattern have not been extensively tuned, so
+          reports about false positives are helpful to us.
+          </p>
+
+          <p>
+          See Weimer and Necula, <i>Finding and Preventing Run-Time Error Handling Mistakes</i>, for
+          a description of the analysis technique.
+          </p>
+          
+      
+<h3><a name="DM_CONVERT_CASE">Dm: Consider using Locale parameterized version of invoked method (DM_CONVERT_CASE)</a></h3>
+
+
+  <p> A String is being converted to upper or lowercase, using the platform's default encoding. This may
+      result in improper conversions when used with international characters. Use the </p>
+      <ul>
+    <li>String.toUpperCase( Locale l )</li>
+    <li>String.toLowerCase( Locale l )</li>
+    </ul>
+      <p>versions instead.</p>
+
+    
+<h3><a name="DM_DEFAULT_ENCODING">Dm: Reliance on default encoding (DM_DEFAULT_ENCODING)</a></h3>
+
+
+<p> Found a call to a method which will perform a byte to String (or String to byte) conversion, and will assume that the default platform encoding is suitable. This will cause the application behaviour to vary between platforms. Use an alternative API and specify a charset name or Charset object explicitly.  </p>
+
+      
+<h3><a name="DP_CREATE_CLASSLOADER_INSIDE_DO_PRIVILEGED">DP: Classloaders should only be created inside doPrivileged block (DP_CREATE_CLASSLOADER_INSIDE_DO_PRIVILEGED)</a></h3>
+
+
+  <p> This code creates a classloader,  which needs permission if a security manage is installed.
+  If this code might be invoked by code that does not
+  have security permissions, then the classloader creation needs to occur inside a doPrivileged block.</p>
+
+    
+<h3><a name="DP_DO_INSIDE_DO_PRIVILEGED">DP: Method invoked that should be only be invoked inside a doPrivileged block (DP_DO_INSIDE_DO_PRIVILEGED)</a></h3>
+
+
+  <p> This code invokes a method that requires a security permission check.
+  If this code will be granted security permissions, but might be invoked by code that does not
+  have security permissions, then the invocation needs to occur inside a doPrivileged block.</p>
+
+    
+<h3><a name="EI_EXPOSE_REP">EI: May expose internal representation by returning reference to mutable object (EI_EXPOSE_REP)</a></h3>
+
+
+  <p> Returning a reference to a mutable object value stored in one of the object's fields
+  exposes the internal representation of the object.&nbsp;
+   If instances
+   are accessed by untrusted code, and unchecked changes to
+   the mutable object would compromise security or other
+   important properties, you will need to do something different.
+  Returning a new copy of the object is better approach in many situations.</p>
+
+    
+<h3><a name="EI_EXPOSE_REP2">EI2: May expose internal representation by incorporating reference to mutable object (EI_EXPOSE_REP2)</a></h3>
+
+
+  <p> This code stores a reference to an externally mutable object into the
+  internal representation of the object.&nbsp;
+   If instances
+   are accessed by untrusted code, and unchecked changes to
+   the mutable object would compromise security or other
+   important properties, you will need to do something different.
+  Storing a copy of the object is better approach in many situations.</p>
+
+    
+<h3><a name="FI_PUBLIC_SHOULD_BE_PROTECTED">FI: Finalizer should be protected, not public (FI_PUBLIC_SHOULD_BE_PROTECTED)</a></h3>
+
+
+  <p> A class's <code>finalize()</code> method should have protected access,
+   not public.</p>
+
+    
+<h3><a name="EI_EXPOSE_STATIC_REP2">MS: May expose internal static state by storing a mutable object into a static field (EI_EXPOSE_STATIC_REP2)</a></h3>
+
+
+  <p> This code stores a reference to an externally mutable object into a static
+   field.
+   If unchecked changes to
+   the mutable object would compromise security or other
+   important properties, you will need to do something different.
+  Storing a copy of the object is better approach in many situations.</p>
+
+    
+<h3><a name="MS_CANNOT_BE_FINAL">MS: Field isn't final and can't be protected from malicious code (MS_CANNOT_BE_FINAL)</a></h3>
+
+
+  <p>
+ A mutable static field could be changed by malicious code or
+        by accident from another package.
+   Unfortunately, the way the field is used doesn't allow
+   any easy fix to this problem.</p>
+
+    
+<h3><a name="MS_EXPOSE_REP">MS: Public static method may expose internal representation by returning array (MS_EXPOSE_REP)</a></h3>
+
+
+  <p> A public static method returns a reference to
+   an array that is part of the static state of the class.
+   Any code that calls this method can freely modify
+   the underlying array.
+   One fix is to return a copy of the array.</p>
+
+    
+<h3><a name="MS_FINAL_PKGPROTECT">MS: Field should be both final and package protected (MS_FINAL_PKGPROTECT)</a></h3>
+
+
+ <p>
+   A mutable static field could be changed by malicious code or
+        by accident from another package.
+        The field could be made package protected and/or made final
+   to avoid
+        this vulnerability.</p>
+
+    
+<h3><a name="MS_MUTABLE_ARRAY">MS: Field is a mutable array (MS_MUTABLE_ARRAY)</a></h3>
+
+
+<p> A final static field references an array
+   and can be accessed by malicious code or
+        by accident from another package.
+   This code can freely modify the contents of the array.</p>
+
+    
+<h3><a name="MS_MUTABLE_HASHTABLE">MS: Field is a mutable Hashtable (MS_MUTABLE_HASHTABLE)</a></h3>
+
+
+ <p>A final static field references a Hashtable
+   and can be accessed by malicious code or
+        by accident from another package.
+   This code can freely modify the contents of the Hashtable.</p>
+
+    
+<h3><a name="MS_OOI_PKGPROTECT">MS: Field should be moved out of an interface and made package protected (MS_OOI_PKGPROTECT)</a></h3>
+
+
+<p>
+ A final static field that is
+defined in an interface references a mutable
+   object such as an array or hashtable.
+   This mutable object could
+   be changed by malicious code or
+        by accident from another package.
+   To solve this, the field needs to be moved to a class
+   and made package protected
+   to avoid
+        this vulnerability.</p>
+
+    
+<h3><a name="MS_PKGPROTECT">MS: Field should be package protected (MS_PKGPROTECT)</a></h3>
+
+
+  <p> A mutable static field could be changed by malicious code or
+   by accident.
+   The field could be made package protected to avoid
+   this vulnerability.</p>
+
+    
+<h3><a name="MS_SHOULD_BE_FINAL">MS: Field isn't final but should be (MS_SHOULD_BE_FINAL)</a></h3>
+
+
+   <p>
+This static field public but not final, and
+could be changed by malicious code or
+        by accident from another package.
+        The field could be made final to avoid
+        this vulnerability.</p>
+
+    
+<h3><a name="MS_SHOULD_BE_REFACTORED_TO_BE_FINAL">MS: Field isn't final but should be refactored to be so (MS_SHOULD_BE_REFACTORED_TO_BE_FINAL)</a></h3>
+
+
+   <p>
+This static field public but not final, and
+could be changed by malicious code or
+by accident from another package.
+The field could be made final to avoid
+this vulnerability. However, the static initializer contains more than one write
+to the field, so doing so will require some refactoring.
+</p>
+
+    
+<h3><a name="AT_OPERATION_SEQUENCE_ON_CONCURRENT_ABSTRACTION">AT: Sequence of calls to concurrent abstraction may not be atomic (AT_OPERATION_SEQUENCE_ON_CONCURRENT_ABSTRACTION)</a></h3>
+
+          
+        <p>This code contains a sequence of calls to a concurrent  abstraction
+            (such as a concurrent hash map).
+            These calls will not be executed atomically.
+          
+      
+<h3><a name="DC_DOUBLECHECK">DC: Possible double check of field (DC_DOUBLECHECK)</a></h3>
+
+
+  <p> This method may contain an instance of double-checked locking.&nbsp;
+  This idiom is not correct according to the semantics of the Java memory
+  model.&nbsp; For more information, see the web page
+  <a href="http://www.cs.umd.edu/~pugh/java/memoryModel/DoubleCheckedLocking.html"
+  >http://www.cs.umd.edu/~pugh/java/memoryModel/DoubleCheckedLocking.html</a>.</p>
+
+    
+<h3><a name="DL_SYNCHRONIZATION_ON_BOOLEAN">DL: Synchronization on Boolean (DL_SYNCHRONIZATION_ON_BOOLEAN)</a></h3>
+
+      
+  <p> The code synchronizes on a boxed primitive constant, such as an Boolean.
+<pre>
+private static Boolean inited = Boolean.FALSE;
+...
+  synchronized(inited) {
+    if (!inited) {
+       init();
+       inited = Boolean.TRUE;
+       }
+     }
+...
+</pre>
+</p>
+<p>Since there normally exist only two Boolean objects, this code could be synchronizing on the same object as other, unrelated code, leading to unresponsiveness
+and possible deadlock</p>
+<p>See CERT <a href="https://www.securecoding.cert.org/confluence/display/java/CON08-J.+Do+not+synchronize+on+objects+that+may+be+reused">CON08-J. Do not synchronize on objects that may be reused</a> for more information.</p>
+
+    
+<h3><a name="DL_SYNCHRONIZATION_ON_BOXED_PRIMITIVE">DL: Synchronization on boxed primitive (DL_SYNCHRONIZATION_ON_BOXED_PRIMITIVE)</a></h3>
+
+      
+  <p> The code synchronizes on a boxed primitive constant, such as an Integer.
+<pre>
+private static Integer count = 0;
+...
+  synchronized(count) {
+     count++;
+     }
+...
+</pre>
+</p>
+<p>Since Integer objects can be cached and shared,
+this code could be synchronizing on the same object as other, unrelated code, leading to unresponsiveness
+and possible deadlock</p>
+<p>See CERT <a href="https://www.securecoding.cert.org/confluence/display/java/CON08-J.+Do+not+synchronize+on+objects+that+may+be+reused">CON08-J. Do not synchronize on objects that may be reused</a> for more information.</p>
+
+    
+<h3><a name="DL_SYNCHRONIZATION_ON_SHARED_CONSTANT">DL: Synchronization on interned String  (DL_SYNCHRONIZATION_ON_SHARED_CONSTANT)</a></h3>
+
+
+  <p> The code synchronizes on interned String.
+<pre>
+private static String LOCK = "LOCK";
+...
+  synchronized(LOCK) { ...}
+...
+</pre>
+</p>
+<p>Constant Strings are interned and shared across all other classes loaded by the JVM. Thus, this could
+is locking on something that other code might also be locking. This could result in very strange and hard to diagnose
+blocking and deadlock behavior. See <a href="http://www.javalobby.org/java/forums/t96352.html">http://www.javalobby.org/java/forums/t96352.html</a> and <a href="http://jira.codehaus.org/browse/JETTY-352">http://jira.codehaus.org/browse/JETTY-352</a>.
+<p>See CERT <a href="https://www.securecoding.cert.org/confluence/display/java/CON08-J.+Do+not+synchronize+on+objects+that+may+be+reused">CON08-J. Do not synchronize on objects that may be reused</a> for more information.</p>
+</p>
+
+    
+<h3><a name="DL_SYNCHRONIZATION_ON_UNSHARED_BOXED_PRIMITIVE">DL: Synchronization on boxed primitive values (DL_SYNCHRONIZATION_ON_UNSHARED_BOXED_PRIMITIVE)</a></h3>
+
+      
+  <p> The code synchronizes on an apparently unshared boxed primitive,
+such as an Integer.
+<pre>
+private static final Integer fileLock = new Integer(1);
+...
+  synchronized(fileLock) {
+     .. do something ..
+     }
+...
+</pre>
+</p>
+<p>It would be much better, in this code, to redeclare fileLock as
+<pre>
+private static final Object fileLock = new Object();
+</pre>
+The existing code might be OK, but it is confusing and a
+future refactoring, such as the "Remove Boxing" refactoring in IntelliJ,
+might replace this with the use of an interned Integer object shared
+throughout the JVM, leading to very confusing behavior and potential deadlock.
+</p>
+
+    
+<h3><a name="DM_MONITOR_WAIT_ON_CONDITION">Dm: Monitor wait() called on Condition (DM_MONITOR_WAIT_ON_CONDITION)</a></h3>
+
+      
+      <p>
+      This method calls <code>wait()</code> on a
+      <code>java.util.concurrent.locks.Condition</code> object.&nbsp;
+      Waiting for a <code>Condition</code> should be done using one of the <code>await()</code>
+      methods defined by the <code>Condition</code> interface.
+      </p>
+      
+   
+<h3><a name="DM_USELESS_THREAD">Dm: A thread was created using the default empty run method (DM_USELESS_THREAD)</a></h3>
+
+
+  <p>This method creates a thread without specifying a run method either by deriving from the Thread class, or
+  by passing a Runnable object. This thread, then, does nothing but waste time.
+</p>
+
+    
+<h3><a name="ESync_EMPTY_SYNC">ESync: Empty synchronized block (ESync_EMPTY_SYNC)</a></h3>
+
+
+  <p> The code contains an empty synchronized block:</p>
+<pre>
+synchronized() {}
+</pre>
+<p>Empty synchronized blocks are far more subtle and hard to use correctly
+than most people recognize, and empty synchronized blocks
+are almost never a better solution
+than less contrived solutions.
+</p>
+
+    
+<h3><a name="IS2_INCONSISTENT_SYNC">IS: Inconsistent synchronization (IS2_INCONSISTENT_SYNC)</a></h3>
+
+
+  <p> The fields of this class appear to be accessed inconsistently with respect
+  to synchronization.&nbsp; This bug report indicates that the bug pattern detector
+  judged that
+  </p>
+  <ul>
+  <li> The class contains a mix of locked and unlocked accesses,</li>
+  <li> At least one locked access was performed by one of the class's own methods, and</li>
+  <li> The number of unsynchronized field accesses (reads and writes) was no more than
+       one third of all accesses, with writes being weighed twice as high as reads</li>
+  </ul>
+
+  <p> A typical bug matching this bug pattern is forgetting to synchronize
+  one of the methods in a class that is intended to be thread-safe.</p>
+
+  <p> You can select the nodes labeled "Unsynchronized access" to show the
+  code locations where the detector believed that a field was accessed
+  without synchronization.</p>
+
+  <p> Note that there are various sources of inaccuracy in this detector;
+  for example, the detector cannot statically detect all situations in which
+  a lock is held.&nbsp; Also, even when the detector is accurate in
+  distinguishing locked vs. unlocked accesses, the code in question may still
+  be correct.</p>
+
+
+    
+<h3><a name="IS_FIELD_NOT_GUARDED">IS: Field not guarded against concurrent access (IS_FIELD_NOT_GUARDED)</a></h3>
+
+
+  <p> This field is annotated with net.jcip.annotations.GuardedBy,
+but can be accessed in a way that seems to violate the annotation.</p>
+
+
+<h3><a name="JLM_JSR166_LOCK_MONITORENTER">JLM: Synchronization performed on Lock (JLM_JSR166_LOCK_MONITORENTER)</a></h3>
+
+
+<p> This method performs synchronization an object that implements
+java.util.concurrent.locks.Lock. Such an object is locked/unlocked
+using
+<code>acquire()</code>/<code>release()</code> rather
+than using the <code>synchronized (...)</code> construct.
+</p>
+
+
+<h3><a name="JLM_JSR166_UTILCONCURRENT_MONITORENTER">JLM: Synchronization performed on util.concurrent instance (JLM_JSR166_UTILCONCURRENT_MONITORENTER)</a></h3>
+
+
+<p> This method performs synchronization an object that is an instance of
+a class from the java.util.concurrent package (or its subclasses). Instances
+of these classes have their own concurrency control mechanisms that are orthogonal to
+the synchronization provided by the Java keyword <code>synchronized</code>. For example,
+synchronizing on an <code>AtomicBoolean</code> will not prevent other threads
+from modifying the  <code>AtomicBoolean</code>.</p>
+<p>Such code may be correct, but should be carefully reviewed and documented,
+and may confuse people who have to maintain the code at a later date.
+</p>
+
+
+<h3><a name="JML_JSR166_CALLING_WAIT_RATHER_THAN_AWAIT">JLM: Using monitor style wait methods on util.concurrent abstraction (JML_JSR166_CALLING_WAIT_RATHER_THAN_AWAIT)</a></h3>
+
+
+<p> This method calls
+<code>wait()</code>,
+<code>notify()</code> or
+<code>notifyAll()()</code>
+on an object that also provides an
+<code>await()</code>,
+<code>signal()</code>,
+<code>signalAll()</code> method (such as util.concurrent Condition objects).
+This probably isn't what you want, and even if you do want it, you should consider changing
+your design, as other developers will find it exceptionally confusing.
+</p>
+
+
+<h3><a name="LI_LAZY_INIT_STATIC">LI: Incorrect lazy initialization of static field (LI_LAZY_INIT_STATIC)</a></h3>
+
+
+<p> This method contains an unsynchronized lazy initialization of a non-volatile static field.
+Because the compiler or processor may reorder instructions,
+threads are not guaranteed to see a completely initialized object,
+<em>if the method can be called by multiple threads</em>.
+You can make the field volatile to correct the problem.
+For more information, see the
+<a href="http://www.cs.umd.edu/~pugh/java/memoryModel/">Java Memory Model web site</a>.
+</p>
+
+    
+<h3><a name="LI_LAZY_INIT_UPDATE_STATIC">LI: Incorrect lazy initialization and update of static field (LI_LAZY_INIT_UPDATE_STATIC)</a></h3>
+
+
+<p> This method contains an unsynchronized lazy initialization of a static field.
+After the field is set, the object stored into that location is further updated or accessed.
+The setting of the field is visible to other threads as soon as it is set. If the
+futher accesses in the method that set the field serve to initialize the object, then
+you have a <em>very serious</em> multithreading bug, unless something else prevents
+any other thread from accessing the stored object until it is fully initialized.
+</p>
+<p>Even if you feel confident that the method is never called by multiple
+threads, it might be better to not set the static field until the value
+you are setting it to is fully populated/initialized.
+
+    
+<h3><a name="ML_SYNC_ON_FIELD_TO_GUARD_CHANGING_THAT_FIELD">ML: Synchronization on field in futile attempt to guard that field (ML_SYNC_ON_FIELD_TO_GUARD_CHANGING_THAT_FIELD)</a></h3>
+
+
+  <p> This method synchronizes on a field in what appears to be an attempt
+to guard against simultaneous updates to that field. But guarding a field
+gets a lock on the referenced object, not on the field. This may not
+provide the mutual exclusion you need, and other threads might
+be obtaining locks on the referenced objects (for other purposes). An example
+of this pattern would be:
+
+<p><pre>
+private Long myNtfSeqNbrCounter = new Long(0);
+private Long getNotificationSequenceNumber() {
+     Long result = null;
+     synchronized(myNtfSeqNbrCounter) {
+         result = new Long(myNtfSeqNbrCounter.longValue() + 1);
+         myNtfSeqNbrCounter = new Long(result.longValue());
+     }
+     return result;
+ }
+</pre>
+
+
+</p>
+
+    
+<h3><a name="ML_SYNC_ON_UPDATED_FIELD">ML: Method synchronizes on an updated field (ML_SYNC_ON_UPDATED_FIELD)</a></h3>
+
+
+  <p> This method synchronizes on an object
+   referenced from a mutable field.
+   This is unlikely to have useful semantics, since different
+threads may be synchronizing on different objects.</p>
+
+    
+<h3><a name="MSF_MUTABLE_SERVLET_FIELD">MSF: Mutable servlet field (MSF_MUTABLE_SERVLET_FIELD)</a></h3>
+
+
+<p>A web server generally only creates one instance of servlet or jsp class (i.e., treats
+the class as a Singleton),
+and will
+have multiple threads invoke methods on that instance to service multiple
+simultaneous requests.
+Thus, having a mutable instance field generally creates race conditions.
+
+    
+<h3><a name="MWN_MISMATCHED_NOTIFY">MWN: Mismatched notify() (MWN_MISMATCHED_NOTIFY)</a></h3>
+
+
+<p> This method calls Object.notify() or Object.notifyAll() without obviously holding a lock
+on the object.&nbsp;  Calling notify() or notifyAll() without a lock held will result in
+an <code>IllegalMonitorStateException</code> being thrown.</p>
+
+    
+<h3><a name="MWN_MISMATCHED_WAIT">MWN: Mismatched wait() (MWN_MISMATCHED_WAIT)</a></h3>
+
+
+<p> This method calls Object.wait() without obviously holding a lock
+on the object.&nbsp;  Calling wait() without a lock held will result in
+an <code>IllegalMonitorStateException</code> being thrown.</p>
+
+    
+<h3><a name="NN_NAKED_NOTIFY">NN: Naked notify (NN_NAKED_NOTIFY)</a></h3>
+
+
+  <p> A call to <code>notify()</code> or <code>notifyAll()</code>
+  was made without any (apparent) accompanying
+  modification to mutable object state.&nbsp; In general, calling a notify
+  method on a monitor is done because some condition another thread is
+  waiting for has become true.&nbsp; However, for the condition to be meaningful,
+  it must involve a heap object that is visible to both threads.</p>
+
+  <p> This bug does not necessarily indicate an error, since the change to
+  mutable object state may have taken place in a method which then called
+  the method containing the notification.</p>
+
+    
+<h3><a name="NP_SYNC_AND_NULL_CHECK_FIELD">NP: Synchronize and null check on the same field. (NP_SYNC_AND_NULL_CHECK_FIELD)</a></h3>
+
+
+<p>Since the field is synchronized on, it seems not likely to be null.
+If it is null and then synchronized on a NullPointerException will be
+thrown and the check would be pointless. Better to synchronize on
+another field.</p>
+
+
+     
+<h3><a name="NO_NOTIFY_NOT_NOTIFYALL">No: Using notify() rather than notifyAll() (NO_NOTIFY_NOT_NOTIFYALL)</a></h3>
+
+
+  <p> This method calls <code>notify()</code> rather than <code>notifyAll()</code>.&nbsp;
+  Java monitors are often used for multiple conditions.&nbsp; Calling <code>notify()</code>
+  only wakes up one thread, meaning that the thread woken up might not be the
+  one waiting for the condition that the caller just satisfied.</p>
+
+    
+<h3><a name="RS_READOBJECT_SYNC">RS: Class's readObject() method is synchronized (RS_READOBJECT_SYNC)</a></h3>
+
+
+  <p> This serializable class defines a <code>readObject()</code> which is
+  synchronized.&nbsp; By definition, an object created by deserialization
+  is only reachable by one thread, and thus there is no need for
+  <code>readObject()</code> to be synchronized.&nbsp; If the <code>readObject()</code>
+  method itself is causing the object to become visible to another thread,
+  that is an example of very dubious coding style.</p>
+
+    
+<h3><a name="RV_RETURN_VALUE_OF_PUTIFABSENT_IGNORED">RV: Return value of putIfAbsent ignored, value passed to putIfAbsent reused (RV_RETURN_VALUE_OF_PUTIFABSENT_IGNORED)</a></h3>
+
+          
+        The <code>putIfAbsent</code> method is typically used to ensure that a
+        single value is associated with a given key (the first value for which put
+        if absent succeeds).
+        If you ignore the return value and retain a reference to the value passed in,
+        you run the risk of retaining a value that is not the one that is associated with the key in the map.
+        If it matters which one you use and you use the one that isn't stored in the map,
+        your program will behave incorrectly.
+          
+      
+<h3><a name="RU_INVOKE_RUN">Ru: Invokes run on a thread (did you mean to start it instead?) (RU_INVOKE_RUN)</a></h3>
+
+
+  <p> This method explicitly invokes <code>run()</code> on an object.&nbsp;
+  In general, classes implement the <code>Runnable</code> interface because
+  they are going to have their <code>run()</code> method invoked in a new thread,
+  in which case <code>Thread.start()</code> is the right method to call.</p>
+
+    
+<h3><a name="SC_START_IN_CTOR">SC: Constructor invokes Thread.start() (SC_START_IN_CTOR)</a></h3>
+
+
+  <p> The constructor starts a thread. This is likely to be wrong if
+   the class is ever extended/subclassed, since the thread will be started
+   before the subclass constructor is started.</p>
+
+    
+<h3><a name="SP_SPIN_ON_FIELD">SP: Method spins on field (SP_SPIN_ON_FIELD)</a></h3>
+
+
+  <p> This method spins in a loop which reads a field.&nbsp; The compiler
+  may legally hoist the read out of the loop, turning the code into an
+  infinite loop.&nbsp; The class should be changed so it uses proper
+  synchronization (including wait and notify calls).</p>
+
+    
+<h3><a name="STCAL_INVOKE_ON_STATIC_CALENDAR_INSTANCE">STCAL: Call to static Calendar (STCAL_INVOKE_ON_STATIC_CALENDAR_INSTANCE)</a></h3>
+
+
+<p>Even though the JavaDoc does not contain a hint about it, Calendars are inherently unsafe for multihtreaded use.
+The detector has found a call to an instance of Calendar that has been obtained via a static
+field. This looks suspicous.</p>
+<p>For more information on this see <a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6231579">Sun Bug #6231579</a>
+and <a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6178997">Sun Bug #6178997</a>.</p>
+
+
+<h3><a name="STCAL_INVOKE_ON_STATIC_DATE_FORMAT_INSTANCE">STCAL: Call to static DateFormat (STCAL_INVOKE_ON_STATIC_DATE_FORMAT_INSTANCE)</a></h3>
+
+
+<p>As the JavaDoc states, DateFormats are inherently unsafe for multithreaded use.
+The detector has found a call to an instance of DateFormat that has been obtained via a static
+field. This looks suspicous.</p>
+<p>For more information on this see <a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6231579">Sun Bug #6231579</a>
+and <a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6178997">Sun Bug #6178997</a>.</p>
+
+
+<h3><a name="STCAL_STATIC_CALENDAR_INSTANCE">STCAL: Static Calendar field (STCAL_STATIC_CALENDAR_INSTANCE)</a></h3>
+
+
+<p>Even though the JavaDoc does not contain a hint about it, Calendars are inherently unsafe for multihtreaded use.
+Sharing a single instance across thread boundaries without proper synchronization will result in erratic behavior of the
+application. Under 1.4 problems seem to surface less often than under Java 5 where you will probably see
+random ArrayIndexOutOfBoundsExceptions or IndexOutOfBoundsExceptions in sun.util.calendar.BaseCalendar.getCalendarDateFromFixedDate().</p>
+<p>You may also experience serialization problems.</p>
+<p>Using an instance field is recommended.</p>
+<p>For more information on this see <a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6231579">Sun Bug #6231579</a>
+and <a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6178997">Sun Bug #6178997</a>.</p>
+
+
+<h3><a name="STCAL_STATIC_SIMPLE_DATE_FORMAT_INSTANCE">STCAL: Static DateFormat (STCAL_STATIC_SIMPLE_DATE_FORMAT_INSTANCE)</a></h3>
+
+
+<p>As the JavaDoc states, DateFormats are inherently unsafe for multithreaded use.
+Sharing a single instance across thread boundaries without proper synchronization will result in erratic behavior of the
+application.</p>
+<p>You may also experience serialization problems.</p>
+<p>Using an instance field is recommended.</p>
+<p>For more information on this see <a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6231579">Sun Bug #6231579</a>
+and <a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6178997">Sun Bug #6178997</a>.</p>
+
+
+<h3><a name="SWL_SLEEP_WITH_LOCK_HELD">SWL: Method calls Thread.sleep() with a lock held (SWL_SLEEP_WITH_LOCK_HELD)</a></h3>
+
+      
+      <p>
+      This method calls Thread.sleep() with a lock held.  This may result
+      in very poor performance and scalability, or a deadlock, since other threads may
+      be waiting to acquire the lock.  It is a much better idea to call
+      wait() on the lock, which releases the lock and allows other threads
+      to run.
+      </p>
+      
+   
+<h3><a name="TLW_TWO_LOCK_WAIT">TLW: Wait with two locks held (TLW_TWO_LOCK_WAIT)</a></h3>
+
+
+  <p> Waiting on a monitor while two locks are held may cause
+  deadlock.
+   &nbsp;
+   Performing a wait only releases the lock on the object
+   being waited on, not any other locks.
+   &nbsp;
+This not necessarily a bug, but is worth examining
+  closely.</p>
+
+    
+<h3><a name="UG_SYNC_SET_UNSYNC_GET">UG: Unsynchronized get method, synchronized set method (UG_SYNC_SET_UNSYNC_GET)</a></h3>
+
+
+  <p> This class contains similarly-named get and set
+  methods where the set method is synchronized and the get method is not.&nbsp;
+  This may result in incorrect behavior at runtime, as callers of the get
+  method will not necessarily see a consistent state for the object.&nbsp;
+  The get method should be made synchronized.</p>
+
+    
+<h3><a name="UL_UNRELEASED_LOCK">UL: Method does not release lock on all paths (UL_UNRELEASED_LOCK)</a></h3>
+
+
+<p> This method acquires a JSR-166 (<code>java.util.concurrent</code>) lock,
+but does not release it on all paths out of the method.  In general, the correct idiom
+for using a JSR-166 lock is:
+</p>
+<pre>
+    Lock l = ...;
+    l.lock();
+    try {
+        // do something
+    } finally {
+        l.unlock();
+    }
+</pre>
+
+    
+<h3><a name="UL_UNRELEASED_LOCK_EXCEPTION_PATH">UL: Method does not release lock on all exception paths (UL_UNRELEASED_LOCK_EXCEPTION_PATH)</a></h3>
+
+
+<p> This method acquires a JSR-166 (<code>java.util.concurrent</code>) lock,
+but does not release it on all exception paths out of the method.  In general, the correct idiom
+for using a JSR-166 lock is:
+</p>
+<pre>
+    Lock l = ...;
+    l.lock();
+    try {
+        // do something
+    } finally {
+        l.unlock();
+    }
+</pre>
+
+    
+<h3><a name="UW_UNCOND_WAIT">UW: Unconditional wait (UW_UNCOND_WAIT)</a></h3>
+
+
+  <p> This method contains a call to <code>java.lang.Object.wait()</code> which
+  is not guarded by conditional control flow.&nbsp; The code should
+    verify that condition it intends to wait for is not already satisfied
+    before calling wait; any previous notifications will be ignored.
+  </p>
+
+    
+<h3><a name="VO_VOLATILE_INCREMENT">VO: An increment to a volatile field isn't atomic (VO_VOLATILE_INCREMENT)</a></h3>
+
+
+<p>This code increments a volatile field. Increments of volatile fields aren't
+atomic. If more than one thread is incrementing the field at the same time,
+increments could be lost.
+</p>
+
+    
+<h3><a name="VO_VOLATILE_REFERENCE_TO_ARRAY">VO: A volatile reference to an array doesn't treat the array elements as volatile (VO_VOLATILE_REFERENCE_TO_ARRAY)</a></h3>
+
+
+<p>This declares a volatile reference to an array, which might not be what
+you want. With a volatile reference to an array, reads and writes of
+the reference to the array are treated as volatile, but the array elements
+are non-volatile. To get volatile array elements, you will need to use
+one of the atomic array classes in java.util.concurrent (provided
+in Java 5.0).</p>
+
+    
+<h3><a name="WL_USING_GETCLASS_RATHER_THAN_CLASS_LITERAL">WL: Synchronization on getClass rather than class literal (WL_USING_GETCLASS_RATHER_THAN_CLASS_LITERAL)</a></h3>
+
+      
+      <p>
+     This instance method synchronizes on <code>this.getClass()</code>. If this class is subclassed,
+     subclasses will synchronize on the class object for the subclass, which isn't likely what was intended.
+     For example, consider this code from java.awt.Label:
+     <pre>
+     private static final String base = "label";
+     private static int nameCounter = 0;
+     String constructComponentName() {
+        synchronized (getClass()) {
+            return base + nameCounter++;
+        }
+     }
+     </pre></p>
+     <p>Subclasses of <code>Label</code> won't synchronize on the same subclass, giving rise to a datarace.
+     Instead, this code should be synchronizing on <code>Label.class</code>
+      <pre>
+     private static final String base = "label";
+     private static int nameCounter = 0;
+     String constructComponentName() {
+        synchronized (Label.class) {
+            return base + nameCounter++;
+        }
+     }
+     </pre></p>
+      <p>Bug pattern contributed by Jason Mehrens</p>
+      
+    
+<h3><a name="WS_WRITEOBJECT_SYNC">WS: Class's writeObject() method is synchronized but nothing else is (WS_WRITEOBJECT_SYNC)</a></h3>
+
+
+  <p> This class has a <code>writeObject()</code> method which is synchronized;
+  however, no other method of the class is synchronized.</p>
+
+    
+<h3><a name="WA_AWAIT_NOT_IN_LOOP">Wa: Condition.await() not in loop  (WA_AWAIT_NOT_IN_LOOP)</a></h3>
+
+
+  <p> This method contains a call to <code>java.util.concurrent.await()</code>
+   (or variants)
+  which is not in a loop.&nbsp; If the object is used for multiple conditions,
+  the condition the caller intended to wait for might not be the one
+  that actually occurred.</p>
+
+    
+<h3><a name="WA_NOT_IN_LOOP">Wa: Wait not in loop  (WA_NOT_IN_LOOP)</a></h3>
+
+
+  <p> This method contains a call to <code>java.lang.Object.wait()</code>
+  which is not in a loop.&nbsp; If the monitor is used for multiple conditions,
+  the condition the caller intended to wait for might not be the one
+  that actually occurred.</p>
+
+    
+<h3><a name="BX_BOXING_IMMEDIATELY_UNBOXED">Bx: Primitive value is boxed and then immediately unboxed (BX_BOXING_IMMEDIATELY_UNBOXED)</a></h3>
+
+
+  <p>A primitive is boxed, and then immediately unboxed. This probably is due to a manual
+    boxing in a place where an unboxed value is required, thus forcing the compiler
+to immediately undo the work of the boxing.
+</p>
+
+    
+<h3><a name="BX_BOXING_IMMEDIATELY_UNBOXED_TO_PERFORM_COERCION">Bx: Primitive value is boxed then unboxed to perform primitive coercion (BX_BOXING_IMMEDIATELY_UNBOXED_TO_PERFORM_COERCION)</a></h3>
+
+
+  <p>A primitive boxed value constructed and then immediately converted into a different primitive type
+(e.g., <code>new Double(d).intValue()</code>). Just perform direct primitive coercion (e.g., <code>(int) d</code>).</p>
+
+    
+<h3><a name="BX_UNBOXING_IMMEDIATELY_REBOXED">Bx: Boxed value is unboxed and then immediately reboxed (BX_UNBOXING_IMMEDIATELY_REBOXED)</a></h3>
+
+
+  <p>A boxed value is unboxed and then immediately reboxed.
+</p>
+
+    
+<h3><a name="DM_BOXED_PRIMITIVE_TOSTRING">Bx: Method allocates a boxed primitive just to call toString (DM_BOXED_PRIMITIVE_TOSTRING)</a></h3>
+
+
+  <p>A boxed primitive is allocated just to call toString(). It is more effective to just use the static
+  form of toString which takes the primitive value. So,</p>
+  <table>
+     <tr><th>Replace...</th><th>With this...</th></tr>
+     <tr><td>new Integer(1).toString()</td><td>Integer.toString(1)</td></tr>
+     <tr><td>new Long(1).toString()</td><td>Long.toString(1)</td></tr>
+     <tr><td>new Float(1.0).toString()</td><td>Float.toString(1.0)</td></tr>
+     <tr><td>new Double(1.0).toString()</td><td>Double.toString(1.0)</td></tr>
+     <tr><td>new Byte(1).toString()</td><td>Byte.toString(1)</td></tr>
+     <tr><td>new Short(1).toString()</td><td>Short.toString(1)</td></tr>
+     <tr><td>new Boolean(true).toString()</td><td>Boolean.toString(true)</td></tr>
+  </table>
+
+    
+<h3><a name="DM_FP_NUMBER_CTOR">Bx: Method invokes inefficient floating-point Number constructor; use static valueOf instead (DM_FP_NUMBER_CTOR)</a></h3>
+
+      
+      <p>
+      Using <code>new Double(double)</code> is guaranteed to always result in a new object whereas
+      <code>Double.valueOf(double)</code> allows caching of values to be done by the compiler, class library, or JVM.
+      Using of cached values avoids object allocation and the code will be faster.
+      </p>
+      <p>
+      Unless the class must be compatible with JVMs predating Java 1.5,
+      use either autoboxing or the <code>valueOf()</code> method when creating instances of <code>Double</code> and <code>Float</code>.
+      </p>
+      
+    
+<h3><a name="DM_NUMBER_CTOR">Bx: Method invokes inefficient Number constructor; use static valueOf instead (DM_NUMBER_CTOR)</a></h3>
+
+      
+      <p>
+      Using <code>new Integer(int)</code> is guaranteed to always result in a new object whereas
+      <code>Integer.valueOf(int)</code> allows caching of values to be done by the compiler, class library, or JVM.
+      Using of cached values avoids object allocation and the code will be faster.
+      </p>
+      <p>
+      Values between -128 and 127 are guaranteed to have corresponding cached instances
+      and using <code>valueOf</code> is approximately 3.5 times faster than using constructor.
+      For values outside the constant range the performance of both styles is the same.
+      </p>
+      <p>
+      Unless the class must be compatible with JVMs predating Java 1.5,
+      use either autoboxing or the <code>valueOf()</code> method when creating instances of
+      <code>Long</code>, <code>Integer</code>, <code>Short</code>, <code>Character</code>, and <code>Byte</code>.
+      </p>
+      
+    
+<h3><a name="DMI_BLOCKING_METHODS_ON_URL">Dm: The equals and hashCode methods of URL are blocking (DMI_BLOCKING_METHODS_ON_URL)</a></h3>
+
+
+  <p> The equals and hashCode
+method of URL perform domain name resolution, this can result in a big performance hit.
+See <a href="http://michaelscharf.blogspot.com/2006/11/javaneturlequals-and-hashcode-make.html">http://michaelscharf.blogspot.com/2006/11/javaneturlequals-and-hashcode-make.html</a> for more information.
+Consider using <code>java.net.URI</code> instead.
+   </p>
+
+    
+<h3><a name="DMI_COLLECTION_OF_URLS">Dm: Maps and sets of URLs can be performance hogs (DMI_COLLECTION_OF_URLS)</a></h3>
+
+
+  <p> This method or field is or uses a Map or Set of URLs. Since both the equals and hashCode
+method of URL perform domain name resolution, this can result in a big performance hit.
+See <a href="http://michaelscharf.blogspot.com/2006/11/javaneturlequals-and-hashcode-make.html">http://michaelscharf.blogspot.com/2006/11/javaneturlequals-and-hashcode-make.html</a> for more information.
+Consider using <code>java.net.URI</code> instead.
+   </p>
+
+    
+<h3><a name="DM_BOOLEAN_CTOR">Dm: Method invokes inefficient Boolean constructor; use Boolean.valueOf(...) instead (DM_BOOLEAN_CTOR)</a></h3>
+
+
+  <p> Creating new instances of <code>java.lang.Boolean</code> wastes
+  memory, since <code>Boolean</code> objects are immutable and there are
+  only two useful values of this type.&nbsp; Use the <code>Boolean.valueOf()</code>
+  method (or Java 1.5 autoboxing) to create <code>Boolean</code> objects instead.</p>
+
+    
+<h3><a name="DM_GC">Dm: Explicit garbage collection; extremely dubious except in benchmarking code (DM_GC)</a></h3>
+
+
+  <p> Code explicitly invokes garbage collection.
+  Except for specific use in benchmarking, this is very dubious.</p>
+  <p>In the past, situations where people have explicitly invoked
+  the garbage collector in routines such as close or finalize methods
+  has led to huge performance black holes. Garbage collection
+   can be expensive. Any situation that forces hundreds or thousands
+   of garbage collections will bring the machine to a crawl.</p>
+
+    
+<h3><a name="DM_NEW_FOR_GETCLASS">Dm: Method allocates an object, only to get the class object (DM_NEW_FOR_GETCLASS)</a></h3>
+
+
+  <p>This method allocates an object just to call getClass() on it, in order to
+  retrieve the Class object for it. It is simpler to just access the .class property of the class.</p>
+
+    
+<h3><a name="DM_NEXTINT_VIA_NEXTDOUBLE">Dm: Use the nextInt method of Random rather than nextDouble to generate a random integer (DM_NEXTINT_VIA_NEXTDOUBLE)</a></h3>
+
+
+  <p>If <code>r</code> is a <code>java.util.Random</code>, you can generate a random number from <code>0</code> to <code>n-1</code>
+using <code>r.nextInt(n)</code>, rather than using <code>(int)(r.nextDouble() * n)</code>.
+</p>
+<p>The argument to nextInt must be positive. If, for example, you want to generate a random
+value from -99 to 0, use <code>-r.nextInt(100)</code>.
+</p>
+
+    
+<h3><a name="DM_STRING_CTOR">Dm: Method invokes inefficient new String(String) constructor (DM_STRING_CTOR)</a></h3>
+
+
+  <p> Using the <code>java.lang.String(String)</code> constructor wastes memory
+  because the object so constructed will be functionally indistinguishable
+  from the <code>String</code> passed as a parameter.&nbsp; Just use the
+  argument <code>String</code> directly.</p>
+
+    
+<h3><a name="DM_STRING_TOSTRING">Dm: Method invokes toString() method on a String (DM_STRING_TOSTRING)</a></h3>
+
+
+  <p> Calling <code>String.toString()</code> is just a redundant operation.
+  Just use the String.</p>
+
+    
+<h3><a name="DM_STRING_VOID_CTOR">Dm: Method invokes inefficient new String() constructor (DM_STRING_VOID_CTOR)</a></h3>
+
+
+  <p> Creating a new <code>java.lang.String</code> object using the
+  no-argument constructor wastes memory because the object so created will
+  be functionally indistinguishable from the empty string constant
+  <code>""</code>.&nbsp; Java guarantees that identical string constants
+  will be represented by the same <code>String</code> object.&nbsp; Therefore,
+  you should just use the empty string constant directly.</p>
+
+    
+<h3><a name="HSC_HUGE_SHARED_STRING_CONSTANT">HSC: Huge string constants is duplicated across multiple class files (HSC_HUGE_SHARED_STRING_CONSTANT)</a></h3>
+
+      
+      <p>
+    A large String constant is duplicated across multiple class files.
+    This is likely because a final field is initialized to a String constant, and the Java language
+    mandates that all references to a final field from other classes be inlined into
+that classfile. See <a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6447475">JDK bug 6447475</a>
+    for a description of an occurrence of this bug in the JDK and how resolving it reduced
+    the size of the JDK by 1 megabyte.
+</p>
+      
+   
+<h3><a name="ITA_INEFFICIENT_TO_ARRAY">ITA: Method uses toArray() with zero-length array argument (ITA_INEFFICIENT_TO_ARRAY)</a></h3>
+
+
+<p> This method uses the toArray() method of a collection derived class, and passes
+in a zero-length prototype array argument.  It is more efficient to use
+<code>myCollection.toArray(new Foo[myCollection.size()])</code>
+If the array passed in is big enough to store all of the
+elements of the collection, then it is populated and returned
+directly. This avoids the need to create a second array
+(by reflection) to return as the result.</p>
+
+    
+<h3><a name="SBSC_USE_STRINGBUFFER_CONCATENATION">SBSC: Method concatenates strings using + in a loop (SBSC_USE_STRINGBUFFER_CONCATENATION)</a></h3>
+
+
+<p> The method seems to be building a String using concatenation in a loop.
+In each iteration, the String is converted to a StringBuffer/StringBuilder,
+   appended to, and converted back to a String.
+   This can lead to a cost quadratic in the number of iterations,
+   as the growing string is recopied in each iteration. </p>
+
+<p>Better performance can be obtained by using
+a StringBuffer (or StringBuilder in Java 1.5) explicitly.</p>
+
+<p> For example:</p>
+<pre>
+  // This is bad
+  String s = "";
+  for (int i = 0; i &lt; field.length; ++i) {
+    s = s + field[i];
+  }
+
+  // This is better
+  StringBuffer buf = new StringBuffer();
+  for (int i = 0; i &lt; field.length; ++i) {
+    buf.append(field[i]);
+  }
+  String s = buf.toString();
+</pre>
+
+    
+<h3><a name="SIC_INNER_SHOULD_BE_STATIC">SIC: Should be a static inner class (SIC_INNER_SHOULD_BE_STATIC)</a></h3>
+
+
+  <p> This class is an inner class, but does not use its embedded reference
+  to the object which created it.&nbsp; This reference makes the instances
+  of the class larger, and may keep the reference to the creator object
+  alive longer than necessary.&nbsp; If possible, the class should be
+   made static.
+</p>
+
+    
+<h3><a name="SIC_INNER_SHOULD_BE_STATIC_ANON">SIC: Could be refactored into a named static inner class (SIC_INNER_SHOULD_BE_STATIC_ANON)</a></h3>
+
+
+  <p> This class is an inner class, but does not use its embedded reference
+  to the object which created it.&nbsp; This reference makes the instances
+  of the class larger, and may keep the reference to the creator object
+  alive longer than necessary.&nbsp; If possible, the class should be
+  made into a <em>static</em> inner class. Since anonymous inner
+classes cannot be marked as static, doing this will require refactoring
+the inner class so that it is a named inner class.</p>
+
+    
+<h3><a name="SIC_INNER_SHOULD_BE_STATIC_NEEDS_THIS">SIC: Could be refactored into a static inner class (SIC_INNER_SHOULD_BE_STATIC_NEEDS_THIS)</a></h3>
+
+
+  <p> This class is an inner class, but does not use its embedded reference
+  to the object which created it except during construction of the
+inner object.&nbsp; This reference makes the instances
+  of the class larger, and may keep the reference to the creator object
+  alive longer than necessary.&nbsp; If possible, the class should be
+  made into a <em>static</em> inner class. Since the reference to the
+   outer object is required during construction of the inner instance,
+   the inner class will need to be refactored so as to
+   pass a reference to the outer instance to the constructor
+   for the inner class.</p>
+
+    
+<h3><a name="SS_SHOULD_BE_STATIC">SS: Unread field: should this field be static? (SS_SHOULD_BE_STATIC)</a></h3>
+
+
+  <p> This class contains an instance final field that
+   is initialized to a compile-time static value.
+   Consider making the field static.</p>
+
+    
+<h3><a name="UM_UNNECESSARY_MATH">UM: Method calls static Math class method on a constant value (UM_UNNECESSARY_MATH)</a></h3>
+
+
+<p> This method uses a static method from java.lang.Math on a constant value. This method's
+result in this case, can be determined statically, and is faster and sometimes more accurate to
+just use the constant. Methods detected are:
+</p>
+<table>
+<tr>
+   <th>Method</th> <th>Parameter</th>
+</tr>
+<tr>
+   <td>abs</td> <td>-any-</td>
+</tr>
+<tr>
+   <td>acos</td> <td>0.0 or 1.0</td>
+</tr>
+<tr>
+   <td>asin</td> <td>0.0 or 1.0</td>
+</tr>
+<tr>
+   <td>atan</td> <td>0.0 or 1.0</td>
+</tr>
+<tr>
+   <td>atan2</td> <td>0.0</td>
+</tr>
+<tr>
+   <td>cbrt</td> <td>0.0 or 1.0</td>
+</tr>
+<tr>
+   <td>ceil</td> <td>-any-</td>
+</tr>
+<tr>
+   <td>cos</td> <td>0.0</td>
+</tr>
+<tr>
+   <td>cosh</td> <td>0.0</td>
+</tr>
+<tr>
+   <td>exp</td> <td>0.0 or 1.0</td>
+</tr>
+<tr>
+   <td>expm1</td> <td>0.0</td>
+</tr>
+<tr>
+   <td>floor</td> <td>-any-</td>
+</tr>
+<tr>
+   <td>log</td> <td>0.0 or 1.0</td>
+</tr>
+<tr>
+   <td>log10</td> <td>0.0 or 1.0</td>
+</tr>
+<tr>
+   <td>rint</td> <td>-any-</td>
+</tr>
+<tr>
+   <td>round</td> <td>-any-</td>
+</tr>
+<tr>
+   <td>sin</td> <td>0.0</td>
+</tr>
+<tr>
+   <td>sinh</td> <td>0.0</td>
+</tr>
+<tr>
+   <td>sqrt</td> <td>0.0 or 1.0</td>
+</tr>
+<tr>
+   <td>tan</td> <td>0.0</td>
+</tr>
+<tr>
+   <td>tanh</td> <td>0.0</td>
+</tr>
+<tr>
+   <td>toDegrees</td> <td>0.0 or 1.0</td>
+</tr>
+<tr>
+   <td>toRadians</td> <td>0.0</td>
+</tr>
+</table>
+
+    
+<h3><a name="UPM_UNCALLED_PRIVATE_METHOD">UPM: Private method is never called (UPM_UNCALLED_PRIVATE_METHOD)</a></h3>
+
+
+<p> This private method is never called. Although it is
+possible that the method will be invoked through reflection,
+it is more likely that the method is never used, and should be
+removed.
+</p>
+
+
+<h3><a name="URF_UNREAD_FIELD">UrF: Unread field (URF_UNREAD_FIELD)</a></h3>
+
+
+  <p> This field is never read.&nbsp; Consider removing it from the class.</p>
+
+    
+<h3><a name="UUF_UNUSED_FIELD">UuF: Unused field (UUF_UNUSED_FIELD)</a></h3>
+
+
+  <p> This field is never used.&nbsp; Consider removing it from the class.</p>
+
+    
+<h3><a name="WMI_WRONG_MAP_ITERATOR">WMI: Inefficient use of keySet iterator instead of entrySet iterator (WMI_WRONG_MAP_ITERATOR)</a></h3>
+
+
+<p> This method accesses the value of a Map entry, using a key that was retrieved from
+a keySet iterator. It is more efficient to use an iterator on the entrySet of the map, to avoid the
+Map.get(key) lookup.</p>
+
+        
+<h3><a name="DMI_CONSTANT_DB_PASSWORD">Dm: Hardcoded constant database password (DMI_CONSTANT_DB_PASSWORD)</a></h3>
+
+      
+    <p>This code creates a database connect using a hardcoded, constant password. Anyone with access to either the source code or the compiled code can
+    easily learn the password.
+</p>
+
+
+    
+<h3><a name="DMI_EMPTY_DB_PASSWORD">Dm: Empty database password (DMI_EMPTY_DB_PASSWORD)</a></h3>
+
+      
+    <p>This code creates a database connect using a blank or empty password. This indicates that the database is not protected by a password.
+</p>
+
+
+    
+<h3><a name="HRS_REQUEST_PARAMETER_TO_COOKIE">HRS: HTTP cookie formed from untrusted input (HRS_REQUEST_PARAMETER_TO_COOKIE)</a></h3>
+
+      
+    <p>This code constructs an HTTP Cookie using an untrusted HTTP parameter. If this cookie is added to an HTTP response, it will allow a HTTP response splitting
+vulnerability. See <a href="http://en.wikipedia.org/wiki/HTTP_response_splitting">http://en.wikipedia.org/wiki/HTTP_response_splitting</a>
+for more information.</p>
+<p>FindBugs looks only for the most blatant, obvious cases of HTTP response splitting.
+If FindBugs found <em>any</em>, you <em>almost certainly</em> have more
+vulnerabilities that FindBugs doesn't report. If you are concerned about HTTP response splitting, you should seriously
+consider using a commercial static analysis or pen-testing tool.
+</p>
+
+
+    
+<h3><a name="HRS_REQUEST_PARAMETER_TO_HTTP_HEADER">HRS: HTTP Response splitting vulnerability (HRS_REQUEST_PARAMETER_TO_HTTP_HEADER)</a></h3>
+
+            
+    <p>This code directly writes an HTTP parameter to an HTTP header, which allows for a HTTP response splitting
+vulnerability. See <a href="http://en.wikipedia.org/wiki/HTTP_response_splitting">http://en.wikipedia.org/wiki/HTTP_response_splitting</a>
+for more information.</p>
+<p>FindBugs looks only for the most blatant, obvious cases of HTTP response splitting.
+If FindBugs found <em>any</em>, you <em>almost certainly</em> have more
+vulnerabilities that FindBugs doesn't report. If you are concerned about HTTP response splitting, you should seriously
+consider using a commercial static analysis or pen-testing tool.
+</p>
+
+
+        
+<h3><a name="PT_ABSOLUTE_PATH_TRAVERSAL">PT: Absolute path traversal in servlet (PT_ABSOLUTE_PATH_TRAVERSAL)</a></h3>
+
+
+    <p>The software uses an HTTP request parameter to construct a pathname that should be within a restricted directory,
+but it does not properly neutralize absolute path sequences such as "/abs/path" that can resolve to a location that is outside of that directory.
+
+See <a href="http://cwe.mitre.org/data/definitions/36.html">http://cwe.mitre.org/data/definitions/36.html</a>
+for more information.</p>
+<p>FindBugs looks only for the most blatant, obvious cases of absolute path traversal.
+If FindBugs found <em>any</em>, you <em>almost certainly</em> have more
+vulnerabilities that FindBugs doesn't report. If you are concerned about absolute path traversal, you should seriously
+consider using a commercial static analysis or pen-testing tool.
+</p>
+
+
+    
+<h3><a name="PT_RELATIVE_PATH_TRAVERSAL">PT: Relative path traversal in servlet (PT_RELATIVE_PATH_TRAVERSAL)</a></h3>
+
+
+    <p>The software uses an HTTP request parameter to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as ".." that can resolve to a location that is outside of that directory.
+
+See <a href="http://cwe.mitre.org/data/definitions/23.html">http://cwe.mitre.org/data/definitions/23.html</a>
+for more information.</p>
+<p>FindBugs looks only for the most blatant, obvious cases of relative path traversal.
+If FindBugs found <em>any</em>, you <em>almost certainly</em> have more
+vulnerabilities that FindBugs doesn't report. If you are concerned about relative path traversal, you should seriously
+consider using a commercial static analysis or pen-testing tool.
+</p>
+
+
+    
+<h3><a name="SQL_NONCONSTANT_STRING_PASSED_TO_EXECUTE">SQL: Nonconstant string passed to execute method on an SQL statement (SQL_NONCONSTANT_STRING_PASSED_TO_EXECUTE)</a></h3>
+
+
+  <p>The method invokes the execute method on an SQL statement with a String that seems
+to be dynamically generated. Consider using
+a prepared statement instead. It is more efficient and less vulnerable to
+SQL injection attacks.
+</p>
+
+    
+<h3><a name="SQL_PREPARED_STATEMENT_GENERATED_FROM_NONCONSTANT_STRING">SQL: A prepared statement is generated from a nonconstant String (SQL_PREPARED_STATEMENT_GENERATED_FROM_NONCONSTANT_STRING)</a></h3>
+
+
+  <p>The code creates an SQL prepared statement from a nonconstant String.
+If unchecked, tainted data from a user is used in building this String, SQL injection could
+be used to make the prepared statement do something unexpected and undesirable.
+</p>
+
+    
+<h3><a name="XSS_REQUEST_PARAMETER_TO_JSP_WRITER">XSS: JSP reflected cross site scripting vulnerability (XSS_REQUEST_PARAMETER_TO_JSP_WRITER)</a></h3>
+
+
+    <p>This code directly writes an HTTP parameter to JSP output, which allows for a cross site scripting
+vulnerability. See <a href="http://en.wikipedia.org/wiki/Cross-site_scripting">http://en.wikipedia.org/wiki/Cross-site_scripting</a>
+for more information.</p>
+<p>FindBugs looks only for the most blatant, obvious cases of cross site scripting.
+If FindBugs found <em>any</em>, you <em>almost certainly</em> have more cross site scripting
+vulnerabilities that FindBugs doesn't report. If you are concerned about cross site scripting, you should seriously
+consider using a commercial static analysis or pen-testing tool.
+</p>
+
+    
+<h3><a name="XSS_REQUEST_PARAMETER_TO_SEND_ERROR">XSS: Servlet reflected cross site scripting vulnerability in error page (XSS_REQUEST_PARAMETER_TO_SEND_ERROR)</a></h3>
+
+
+    <p>This code directly writes an HTTP parameter to a Server error page (using HttpServletResponse.sendError). Echoing this untrusted input allows
+for a reflected cross site scripting
+vulnerability. See <a href="http://en.wikipedia.org/wiki/Cross-site_scripting">http://en.wikipedia.org/wiki/Cross-site_scripting</a>
+for more information.</p>
+<p>FindBugs looks only for the most blatant, obvious cases of cross site scripting.
+If FindBugs found <em>any</em>, you <em>almost certainly</em> have more cross site scripting
+vulnerabilities that FindBugs doesn't report. If you are concerned about cross site scripting, you should seriously
+consider using a commercial static analysis or pen-testing tool.
+</p>
+
+
+    
+<h3><a name="XSS_REQUEST_PARAMETER_TO_SERVLET_WRITER">XSS: Servlet reflected cross site scripting vulnerability (XSS_REQUEST_PARAMETER_TO_SERVLET_WRITER)</a></h3>
+
+
+    <p>This code directly writes an HTTP parameter to Servlet output, which allows for a reflected cross site scripting
+vulnerability. See <a href="http://en.wikipedia.org/wiki/Cross-site_scripting">http://en.wikipedia.org/wiki/Cross-site_scripting</a>
+for more information.</p>
+<p>FindBugs looks only for the most blatant, obvious cases of cross site scripting.
+If FindBugs found <em>any</em>, you <em>almost certainly</em> have more cross site scripting
+vulnerabilities that FindBugs doesn't report. If you are concerned about cross site scripting, you should seriously
+consider using a commercial static analysis or pen-testing tool.
+</p>
+
+
+    
+<h3><a name="BC_BAD_CAST_TO_ABSTRACT_COLLECTION">BC: Questionable cast to abstract collection  (BC_BAD_CAST_TO_ABSTRACT_COLLECTION)</a></h3>
+
+
+<p>
+This code casts a Collection to an abstract collection
+(such as <code>List</code>, <code>Set</code>, or <code>Map</code>).
+Ensure that you are guaranteed that the object is of the type
+you are casting to. If all you need is to be able
+to iterate through a collection, you don't need to cast it to a Set or List.
+</p>
+
+    
+<h3><a name="BC_BAD_CAST_TO_CONCRETE_COLLECTION">BC: Questionable cast to concrete collection (BC_BAD_CAST_TO_CONCRETE_COLLECTION)</a></h3>
+
+
+<p>
+This code casts an abstract collection (such as a Collection, List, or Set)
+to a specific concrete implementation (such as an ArrayList or HashSet).
+This might not be correct, and it may make your code fragile, since
+it makes it harder to switch to other concrete implementations at a future
+point. Unless you have a particular reason to do so, just use the abstract
+collection class.
+</p>
+
+    
+<h3><a name="BC_UNCONFIRMED_CAST">BC: Unchecked/unconfirmed cast (BC_UNCONFIRMED_CAST)</a></h3>
+
+
+<p>
+This cast is unchecked, and not all instances of the type casted from can be cast to
+the type it is being cast to. Check that your program logic ensures that this
+cast will not fail.
+</p>
+
+    
+<h3><a name="BC_UNCONFIRMED_CAST_OF_RETURN_VALUE">BC: Unchecked/unconfirmed cast of return value from method (BC_UNCONFIRMED_CAST_OF_RETURN_VALUE)</a></h3>
+
+
+<p>
+This code performs an unchecked cast of the return value of a method.
+The code might be calling the method in such a way that the cast is guaranteed to be
+safe, but FindBugs is unable to verify that the cast is safe.  Check that your program logic ensures that this
+cast will not fail.
+</p>
+
+    
+<h3><a name="BC_VACUOUS_INSTANCEOF">BC: instanceof will always return true (BC_VACUOUS_INSTANCEOF)</a></h3>
+
+
+<p>
+This instanceof test will always return true (unless the value being tested is null).
+Although this is safe, make sure it isn't
+an indication of some misunderstanding or some other logic error.
+If you really want to test the value for being null, perhaps it would be clearer to do
+better to do a null test rather than an instanceof test.
+</p>
+
+    
+<h3><a name="ICAST_QUESTIONABLE_UNSIGNED_RIGHT_SHIFT">BSHIFT: Unsigned right shift cast to short/byte (ICAST_QUESTIONABLE_UNSIGNED_RIGHT_SHIFT)</a></h3>
+
+
+<p>
+The code performs an unsigned right shift, whose result is then
+cast to a short or byte, which discards the upper bits of the result.
+Since the upper bits are discarded, there may be no difference between
+a signed and unsigned right shift (depending upon the size of the shift).
+</p>
+
+    
+<h3><a name="CI_CONFUSED_INHERITANCE">CI: Class is final but declares protected field (CI_CONFUSED_INHERITANCE)</a></h3>
+
+      
+      <p>
+      This class is declared to be final, but declares fields to be protected. Since the class
+      is final, it can not be derived from, and the use of protected is confusing. The access
+      modifier for the field should be changed to private or public to represent the true
+      use for the field.
+      </p>
+      
+    
+<h3><a name="DB_DUPLICATE_BRANCHES">DB: Method uses the same code for two branches (DB_DUPLICATE_BRANCHES)</a></h3>
+
+      
+      <p>
+      This method uses the same code to implement two branches of a conditional branch.
+    Check to ensure that this isn't a coding mistake.
+      </p>
+      
+   
+<h3><a name="DB_DUPLICATE_SWITCH_CLAUSES">DB: Method uses the same code for two switch clauses (DB_DUPLICATE_SWITCH_CLAUSES)</a></h3>
+
+      
+      <p>
+      This method uses the same code to implement two clauses of a switch statement.
+    This could be a case of duplicate code, but it might also indicate
+    a coding mistake.
+      </p>
+      
+   
+<h3><a name="DLS_DEAD_LOCAL_STORE">DLS: Dead store to local variable (DLS_DEAD_LOCAL_STORE)</a></h3>
+
+
+<p>
+This instruction assigns a value to a local variable,
+but the value is not read or used in any subsequent instruction.
+Often, this indicates an error, because the value computed is never
+used.
+</p>
+<p>
+Note that Sun's javac compiler often generates dead stores for
+final local variables.  Because FindBugs is a bytecode-based tool,
+there is no easy way to eliminate these false positives.
+</p>
+
+    
+<h3><a name="DLS_DEAD_LOCAL_STORE_IN_RETURN">DLS: Useless assignment in return statement (DLS_DEAD_LOCAL_STORE_IN_RETURN)</a></h3>
+
+      
+<p>
+This statement assigns to a local variable in a return statement. This assignment
+has effect. Please verify that this statement does the right thing.
+</p>
+
+    
+<h3><a name="DLS_DEAD_LOCAL_STORE_OF_NULL">DLS: Dead store of null to local variable (DLS_DEAD_LOCAL_STORE_OF_NULL)</a></h3>
+
+
+<p>The code stores null into a local variable, and the stored value is not
+read. This store may have been introduced to assist the garbage collector, but
+as of Java SE 6.0, this is no longer needed or useful.
+</p>
+
+    
+<h3><a name="DLS_DEAD_LOCAL_STORE_SHADOWS_FIELD">DLS: Dead store to local variable that shadows field (DLS_DEAD_LOCAL_STORE_SHADOWS_FIELD)</a></h3>
+
+
+<p>
+This instruction assigns a value to a local variable,
+but the value is not read or used in any subsequent instruction.
+Often, this indicates an error, because the value computed is never
+used. There is a field with the same name as the local variable. Did you
+mean to assign to that variable instead?
+</p>
+
+    
+<h3><a name="DMI_HARDCODED_ABSOLUTE_FILENAME">DMI: Code contains a hard coded reference to an absolute pathname (DMI_HARDCODED_ABSOLUTE_FILENAME)</a></h3>
+
+
+<p>This code constructs a File object using a hard coded to an absolute pathname
+(e.g., <code>new File("/home/dannyc/workspace/j2ee/src/share/com/sun/enterprise/deployment");</code>
+</p>
+
+    
+<h3><a name="DMI_NONSERIALIZABLE_OBJECT_WRITTEN">DMI: Non serializable object written to ObjectOutput (DMI_NONSERIALIZABLE_OBJECT_WRITTEN)</a></h3>
+
+
+<p>
+This code seems to be passing a non-serializable object to the ObjectOutput.writeObject method.
+If the object is, indeed, non-serializable, an error will result.
+</p>
+
+    
+<h3><a name="DMI_USELESS_SUBSTRING">DMI: Invocation of substring(0), which returns the original value (DMI_USELESS_SUBSTRING)</a></h3>
+
+
+<p>
+This code invokes substring(0) on a String, which returns the original value.
+</p>
+
+    
+<h3><a name="DMI_THREAD_PASSED_WHERE_RUNNABLE_EXPECTED">Dm: Thread passed where Runnable expected (DMI_THREAD_PASSED_WHERE_RUNNABLE_EXPECTED)</a></h3>
+
+
+  <p> A Thread object is passed as a parameter to a method where
+a Runnable is expected. This is rather unusual, and may indicate a logic error
+or cause unexpected behavior.
+   </p>
+
+    
+<h3><a name="EQ_DOESNT_OVERRIDE_EQUALS">Eq: Class doesn't override equals in superclass (EQ_DOESNT_OVERRIDE_EQUALS)</a></h3>
+
+
+  <p> This class extends a class that defines an equals method and adds fields, but doesn't
+define an equals method itself. Thus, equality on instances of this class will
+ignore the identity of the subclass and the added fields. Be sure this is what is intended,
+and that you don't need to override the equals method. Even if you don't need to override
+the equals method, consider overriding it anyway to document the fact
+that the equals method for the subclass just return the result of
+invoking super.equals(o).
+  </p>
+
+    
+<h3><a name="EQ_UNUSUAL">Eq: Unusual equals method  (EQ_UNUSUAL)</a></h3>
+
+
+  <p> This class doesn't do any of the patterns we recognize for checking that the type of the argument
+is compatible with the type of the <code>this</code> object. There might not be anything wrong with
+this code, but it is worth reviewing.
+</p>
+
+    
+<h3><a name="FE_FLOATING_POINT_EQUALITY">FE: Test for floating point equality (FE_FLOATING_POINT_EQUALITY)</a></h3>
+
+   
+    <p>
+    This operation compares two floating point values for equality.
+    Because floating point calculations may involve rounding,
+   calculated float and double values may not be accurate.
+    For values that must be precise, such as monetary values,
+   consider using a fixed-precision type such as BigDecimal.
+    For values that need not be precise, consider comparing for equality
+    within some range, for example:
+    <code>if ( Math.abs(x - y) &lt; .0000001 )</code>.
+   See the Java Language Specification, section 4.2.4.
+    </p>
+    
+     
+<h3><a name="VA_FORMAT_STRING_BAD_CONVERSION_TO_BOOLEAN">FS: Non-Boolean argument formatted using %b format specifier (VA_FORMAT_STRING_BAD_CONVERSION_TO_BOOLEAN)</a></h3>
+
+
+<p>
+An argument not of type Boolean is being formatted with a %b format specifier. This won't throw an
+exception; instead, it will print true for any nonnull value, and false for null.
+This feature of format strings is strange, and may not be what you intended.
+</p>
+
+     
+<h3><a name="IA_AMBIGUOUS_INVOCATION_OF_INHERITED_OR_OUTER_METHOD">IA: Ambiguous invocation of either an inherited or outer method (IA_AMBIGUOUS_INVOCATION_OF_INHERITED_OR_OUTER_METHOD)</a></h3>
+
+
+  <p> An inner class is invoking a method that could be resolved to either a inherited method or a method defined in an outer class. By the Java semantics,
+it will be resolved to invoke the inherited method, but this may not be want
+you intend. If you really intend to invoke the inherited method,
+invoke it by invoking the method on super (e.g., invoke super.foo(17)), and
+thus it will be clear to other readers of your code and to FindBugs
+that you want to invoke the inherited method, not the method in the outer class.
+</p>
+
+    
+<h3><a name="IC_INIT_CIRCULARITY">IC: Initialization circularity (IC_INIT_CIRCULARITY)</a></h3>
+
+
+  <p> A circularity was detected in the static initializers of the two
+  classes referenced by the bug instance.&nbsp; Many kinds of unexpected
+  behavior may arise from such circularity.</p>
+
+    
+<h3><a name="ICAST_IDIV_CAST_TO_DOUBLE">ICAST: integral division result cast to double or float (ICAST_IDIV_CAST_TO_DOUBLE)</a></h3>
+
+
+<p>
+This code casts the result of an integral division (e.g., int or long division)
+operation to double or
+float.
+Doing division on integers truncates the result
+to the integer value closest to zero.  The fact that the result
+was cast to double suggests that this precision should have been retained.
+What was probably meant was to cast one or both of the operands to
+double <em>before</em> performing the division.  Here is an example:
+</p>
+<blockquote>
+<pre>
+int x = 2;
+int y = 5;
+// Wrong: yields result 0.0
+double value1 =  x / y;
+
+// Right: yields result 0.4
+double value2 =  x / (double) y;
+</pre>
+</blockquote>
+
+    
+<h3><a name="ICAST_INTEGER_MULTIPLY_CAST_TO_LONG">ICAST: Result of integer multiplication cast to long (ICAST_INTEGER_MULTIPLY_CAST_TO_LONG)</a></h3>
+
+
+<p>
+This code performs integer multiply and then converts the result to a long,
+as in:
+<code>
+<pre>
+    long convertDaysToMilliseconds(int days) { return 1000*3600*24*days; }
+</pre></code>
+If the multiplication is done using long arithmetic, you can avoid
+the possibility that the result will overflow. For example, you
+could fix the above code to:
+<code>
+<pre>
+    long convertDaysToMilliseconds(int days) { return 1000L*3600*24*days; }
+</pre></code>
+or
+<code>
+<pre>
+    static final long MILLISECONDS_PER_DAY = 24L*3600*1000;
+    long convertDaysToMilliseconds(int days) { return days * MILLISECONDS_PER_DAY; }
+</pre></code>
+</p>
+
+
+    
+<h3><a name="IM_AVERAGE_COMPUTATION_COULD_OVERFLOW">IM: Computation of average could overflow (IM_AVERAGE_COMPUTATION_COULD_OVERFLOW)</a></h3>
+
+
+<p>The code computes the average of two integers using either division or signed right shift,
+and then uses the result as the index of an array.
+If the values being averaged are very large, this can overflow (resulting in the computation
+of a negative average).  Assuming that the result is intended to be nonnegative, you
+can use an unsigned right shift instead. In other words, rather that using <code>(low+high)/2</code>,
+use <code>(low+high) &gt;&gt;&gt; 1</code>
+</p>
+<p>This bug exists in many earlier implementations of binary search and merge sort.
+Martin Buchholz <a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6412541">found and fixed it</a>
+in the JDK libraries, and Joshua Bloch
+<a href="http://googleresearch.blogspot.com/2006/06/extra-extra-read-all-about-it-nearly.html">widely
+publicized the bug pattern</a>.
+</p>
+
+    
+<h3><a name="IM_BAD_CHECK_FOR_ODD">IM: Check for oddness that won't work for negative numbers  (IM_BAD_CHECK_FOR_ODD)</a></h3>
+
+
+<p>
+The code uses x % 2 == 1 to check to see if a value is odd, but this won't work
+for negative numbers (e.g., (-5) % 2 == -1). If this code is intending to check
+for oddness, consider using x &amp; 1 == 1, or x % 2 != 0.
+</p>
+
+    
+<h3><a name="INT_BAD_REM_BY_1">INT: Integer remainder modulo 1 (INT_BAD_REM_BY_1)</a></h3>
+
+
+<p> Any expression (exp % 1) is guaranteed to always return zero.
+Did you mean (exp &amp; 1) or (exp % 2) instead?
+</p>
+
+    
+<h3><a name="INT_VACUOUS_BIT_OPERATION">INT: Vacuous bit mask operation on integer value (INT_VACUOUS_BIT_OPERATION)</a></h3>
+
+
+<p> This is an integer bit operation (and, or, or exclusive or) that doesn't do any useful work
+(e.g., <code>v & 0xffffffff</code>).
+
+</p>
+
+    
+<h3><a name="INT_VACUOUS_COMPARISON">INT: Vacuous comparison of integer value (INT_VACUOUS_COMPARISON)</a></h3>
+
+
+<p> There is an integer comparison that always returns
+the same value (e.g., x &lt;= Integer.MAX_VALUE).
+</p>
+
+    
+<h3><a name="MTIA_SUSPECT_SERVLET_INSTANCE_FIELD">MTIA: Class extends Servlet class and uses instance variables (MTIA_SUSPECT_SERVLET_INSTANCE_FIELD)</a></h3>
+
+   
+    <p>
+    This class extends from a Servlet class, and uses an instance member variable. Since only
+    one instance of a Servlet class is created by the J2EE framework, and used in a
+    multithreaded way, this paradigm is highly discouraged and most likely problematic. Consider
+    only using method local variables.
+    </p>
+    
+      
+<h3><a name="MTIA_SUSPECT_STRUTS_INSTANCE_FIELD">MTIA: Class extends Struts Action class and uses instance variables (MTIA_SUSPECT_STRUTS_INSTANCE_FIELD)</a></h3>
+
+   
+    <p>
+    This class extends from a Struts Action class, and uses an instance member variable. Since only
+    one instance of a struts Action class is created by the Struts framework, and used in a
+    multithreaded way, this paradigm is highly discouraged and most likely problematic. Consider
+    only using method local variables. Only instance fields that are written outside of a monitor
+    are reported.
+    </p>
+    
+      
+<h3><a name="NP_DEREFERENCE_OF_READLINE_VALUE">NP: Dereference of the result of readLine() without nullcheck (NP_DEREFERENCE_OF_READLINE_VALUE)</a></h3>
+
+
+  <p> The result of invoking readLine() is dereferenced without checking to see if the result is null. If there are no more lines of text
+to read, readLine() will return null and dereferencing that will generate a null pointer exception.
+</p>
+
+    
+<h3><a name="NP_IMMEDIATE_DEREFERENCE_OF_READLINE">NP: Immediate dereference of the result of readLine() (NP_IMMEDIATE_DEREFERENCE_OF_READLINE)</a></h3>
+
+
+  <p> The result of invoking readLine() is immediately dereferenced. If there are no more lines of text
+to read, readLine() will return null and dereferencing that will generate a null pointer exception.
+</p>
+
+    
+<h3><a name="NP_LOAD_OF_KNOWN_NULL_VALUE">NP: Load of known null value (NP_LOAD_OF_KNOWN_NULL_VALUE)</a></h3>
+
+
+  <p> The variable referenced at this point is known to be null due to an earlier
+   check against null. Although this is valid, it might be a mistake (perhaps you
+intended to refer to a different variable, or perhaps the earlier check to see if the
+variable is null should have been a check to see if it was nonnull).
+</p>
+
+    
+<h3><a name="NP_NULL_ON_SOME_PATH_FROM_RETURN_VALUE">NP: Possible null pointer dereference due to return value of called method (NP_NULL_ON_SOME_PATH_FROM_RETURN_VALUE)</a></h3>
+
+      
+<p> The return value from a method is dereferenced without a null check,
+and the return value of that method is one that should generally be checked
+for null.  This may lead to a <code>NullPointerException</code> when the code is executed.
+</p>
+      
+   
+<h3><a name="NP_NULL_ON_SOME_PATH_MIGHT_BE_INFEASIBLE">NP: Possible null pointer dereference on branch that might be infeasible (NP_NULL_ON_SOME_PATH_MIGHT_BE_INFEASIBLE)</a></h3>
+
+
+<p> There is a branch of statement that, <em>if executed,</em>  guarantees that
+a null value will be dereferenced, which
+would generate a <code>NullPointerException</code> when the code is executed.
+Of course, the problem might be that the branch or statement is infeasible and that
+the null pointer exception can't ever be executed; deciding that is beyond the ability of FindBugs.
+Due to the fact that this value had been previously tested for nullness,
+this is a definite possibility.
+</p>
+
+    
+<h3><a name="NP_PARAMETER_MUST_BE_NONNULL_BUT_MARKED_AS_NULLABLE">NP: Parameter must be nonnull but is marked as nullable (NP_PARAMETER_MUST_BE_NONNULL_BUT_MARKED_AS_NULLABLE)</a></h3>
+
+
+<p> This parameter is always used in a way that requires it to be nonnull,
+but the parameter is explicitly annotated as being Nullable. Either the use
+of the parameter or the annotation is wrong.
+</p>
+
+    
+<h3><a name="NP_UNWRITTEN_PUBLIC_OR_PROTECTED_FIELD">NP: Read of unwritten public or protected field (NP_UNWRITTEN_PUBLIC_OR_PROTECTED_FIELD)</a></h3>
+
+
+  <p> The program is dereferencing a public or protected
+field that does not seem to ever have a non-null value written to it.
+Unless the field is initialized via some mechanism not seen by the analysis,
+dereferencing this value will generate a null pointer exception.
+</p>
+
+    
+<h3><a name="NS_DANGEROUS_NON_SHORT_CIRCUIT">NS: Potentially dangerous use of non-short-circuit logic (NS_DANGEROUS_NON_SHORT_CIRCUIT)</a></h3>
+
+
+  <p> This code seems to be using non-short-circuit logic (e.g., &amp;
+or |)
+rather than short-circuit logic (&amp;&amp; or ||). In addition,
+it seem possible that, depending on the value of the left hand side, you might not
+want to evaluate the right hand side (because it would have side effects, could cause an exception
+or could be expensive.</p>
+<p>
+Non-short-circuit logic causes both sides of the expression
+to be evaluated even when the result can be inferred from
+knowing the left-hand side. This can be less efficient and
+can result in errors if the left-hand side guards cases
+when evaluating the right-hand side can generate an error.
+</p>
+
+<p>See <a href="http://java.sun.com/docs/books/jls/third_edition/html/expressions.html#15.22.2">the Java
+Language Specification</a> for details
+
+</p>
+
+    
+<h3><a name="NS_NON_SHORT_CIRCUIT">NS: Questionable use of non-short-circuit logic (NS_NON_SHORT_CIRCUIT)</a></h3>
+
+
+  <p> This code seems to be using non-short-circuit logic (e.g., &amp;
+or |)
+rather than short-circuit logic (&amp;&amp; or ||).
+Non-short-circuit logic causes both sides of the expression
+to be evaluated even when the result can be inferred from
+knowing the left-hand side. This can be less efficient and
+can result in errors if the left-hand side guards cases
+when evaluating the right-hand side can generate an error.
+
+<p>See <a href="http://java.sun.com/docs/books/jls/third_edition/html/expressions.html#15.22.2">the Java
+Language Specification</a> for details
+
+</p>
+
+    
+<h3><a name="PZLA_PREFER_ZERO_LENGTH_ARRAYS">PZLA: Consider returning a zero length array rather than null (PZLA_PREFER_ZERO_LENGTH_ARRAYS)</a></h3>
+
+
+<p> It is often a better design to
+return a length zero array rather than a null reference to indicate that there
+are no results (i.e., an empty list of results).
+This way, no explicit check for null is needed by clients of the method.</p>
+
+<p>On the other hand, using null to indicate
+"there is no answer to this question" is probably appropriate.
+For example, <code>File.listFiles()</code> returns an empty list
+if given a directory containing no files, and returns null if the file
+is not a directory.</p>
+
+    
+<h3><a name="QF_QUESTIONABLE_FOR_LOOP">QF: Complicated, subtle or wrong increment in for-loop  (QF_QUESTIONABLE_FOR_LOOP)</a></h3>
+
+
+   <p>Are you sure this for loop is incrementing the correct variable?
+   It appears that another variable is being initialized and checked
+   by the for loop.
+</p>
+
+    
+<h3><a name="RCN_REDUNDANT_COMPARISON_OF_NULL_AND_NONNULL_VALUE">RCN: Redundant comparison of non-null value to null (RCN_REDUNDANT_COMPARISON_OF_NULL_AND_NONNULL_VALUE)</a></h3>
+
+
+<p> This method contains a reference known to be non-null with another reference
+known to be null.</p>
+
+    
+<h3><a name="RCN_REDUNDANT_COMPARISON_TWO_NULL_VALUES">RCN: Redundant comparison of two null values (RCN_REDUNDANT_COMPARISON_TWO_NULL_VALUES)</a></h3>
+
+
+<p> This method contains a redundant comparison of two references known to
+both be definitely null.</p>
+
+    
+<h3><a name="RCN_REDUNDANT_NULLCHECK_OF_NONNULL_VALUE">RCN: Redundant nullcheck of value known to be non-null (RCN_REDUNDANT_NULLCHECK_OF_NONNULL_VALUE)</a></h3>
+
+
+<p> This method contains a redundant check of a known non-null value against
+the constant null.</p>
+
+    
+<h3><a name="RCN_REDUNDANT_NULLCHECK_OF_NULL_VALUE">RCN: Redundant nullcheck of value known to be null (RCN_REDUNDANT_NULLCHECK_OF_NULL_VALUE)</a></h3>
+
+
+<p> This method contains a redundant check of a known null value against
+the constant null.</p>
+
+    
+<h3><a name="REC_CATCH_EXCEPTION">REC: Exception is caught when Exception is not thrown (REC_CATCH_EXCEPTION)</a></h3>
+
+  
+  <p>
+  This method uses a try-catch block that catches Exception objects, but Exception is not
+  thrown within the try block, and RuntimeException is not explicitly caught.  It is a common bug pattern to
+  say try { ... } catch (Exception e) { something } as a shorthand for catching a number of types of exception
+  each of whose catch blocks is identical, but this construct also accidentally catches RuntimeException as well,
+  masking potential bugs.
+  </p>
+  
+     
+<h3><a name="RI_REDUNDANT_INTERFACES">RI: Class implements same interface as superclass (RI_REDUNDANT_INTERFACES)</a></h3>
+
+   
+    <p>
+    This class declares that it implements an interface that is also implemented by a superclass.
+    This is redundant because once a superclass implements an interface, all subclasses by default also
+    implement this interface. It may point out that the inheritance hierarchy has changed since
+    this class was created, and consideration should be given to the ownership of
+    the interface's implementation.
+    </p>
+    
+     
+<h3><a name="RV_CHECK_FOR_POSITIVE_INDEXOF">RV: Method checks to see if result of String.indexOf is positive (RV_CHECK_FOR_POSITIVE_INDEXOF)</a></h3>
+
+
+   <p> The method invokes String.indexOf and checks to see if the result is positive or non-positive.
+   It is much more typical to check to see if the result is negative or non-negative. It is
+   positive only if the substring checked for occurs at some place other than at the beginning of
+   the String.</p>
+
+    
+<h3><a name="RV_DONT_JUST_NULL_CHECK_READLINE">RV: Method discards result of readLine after checking if it is nonnull (RV_DONT_JUST_NULL_CHECK_READLINE)</a></h3>
+
+
+   <p> The value returned by readLine is discarded after checking to see if the return
+value is non-null. In almost all situations, if the result is non-null, you will want
+to use that non-null value. Calling readLine again will give you a different line.</p>
+
+    
+<h3><a name="RV_REM_OF_HASHCODE">RV: Remainder of hashCode could be negative (RV_REM_OF_HASHCODE)</a></h3>
+
+
+<p> This code computes a hashCode, and then computes
+the remainder of that value modulo another value. Since the hashCode
+can be negative, the result of the remainder operation
+can also be negative. </p>
+<p> Assuming you want to ensure that the result of your computation is nonnegative,
+you may need to change your code.
+If you know the divisor is a power of 2,
+you can use a bitwise and operator instead (i.e., instead of
+using <code>x.hashCode()%n</code>, use <code>x.hashCode()&amp;(n-1)</code>.
+This is probably faster than computing the remainder as well.
+If you don't know that the divisor is a power of 2, take the absolute
+value of the result of the remainder operation (i.e., use
+<code>Math.abs(x.hashCode()%n)</code>
+</p>
+
+    
+<h3><a name="RV_REM_OF_RANDOM_INT">RV: Remainder of 32-bit signed random integer (RV_REM_OF_RANDOM_INT)</a></h3>
+
+
+<p> This code generates a random signed integer and then computes
+the remainder of that value modulo another value. Since the random
+number can be negative, the result of the remainder operation
+can also be negative. Be sure this is intended, and strongly
+consider using the Random.nextInt(int) method instead.
+</p>
+
+    
+<h3><a name="RV_RETURN_VALUE_IGNORED_INFERRED">RV: Method ignores return value, is this OK? (RV_RETURN_VALUE_IGNORED_INFERRED)</a></h3>
+
+
+<p>This code calls a method and ignores the return value. The return value
+is the same type as the type the method is invoked on, and from our analysis it looks
+like the return value might be important (e.g., like ignoring the
+return value of <code>String.toLowerCase()</code>).
+</p>
+<p>We are guessing that ignoring the return value might be a bad idea just from
+a simple analysis of the body of the method. You can use a @CheckReturnValue annotation
+to instruct FindBugs as to whether ignoring the return value of this method
+is important or acceptable.
+</p>
+<p>Please investigate this closely to decide whether it is OK to ignore the return value.
+</p>
+
+    
+<h3><a name="SA_FIELD_DOUBLE_ASSIGNMENT">SA: Double assignment of field (SA_FIELD_DOUBLE_ASSIGNMENT)</a></h3>
+
+
+<p> This method contains a double assignment of a field; e.g.
+</p>
+<pre>
+  int x,y;
+  public void foo() {
+    x = x = 17;
+  }
+</pre>
+<p>Assigning to a field twice is useless, and may indicate a logic error or typo.</p>
+
+    
+<h3><a name="SA_LOCAL_DOUBLE_ASSIGNMENT">SA: Double assignment of local variable  (SA_LOCAL_DOUBLE_ASSIGNMENT)</a></h3>
+
+
+<p> This method contains a double assignment of a local variable; e.g.
+</p>
+<pre>
+  public void foo() {
+    int x,y;
+    x = x = 17;
+  }
+</pre>
+<p>Assigning the same value to a variable twice is useless, and may indicate a logic error or typo.</p>
+
+    
+<h3><a name="SA_LOCAL_SELF_ASSIGNMENT">SA: Self assignment of local variable (SA_LOCAL_SELF_ASSIGNMENT)</a></h3>
+
+
+<p> This method contains a self assignment of a local variable; e.g.</p>
+<pre>
+  public void foo() {
+    int x = 3;
+    x = x;
+  }
+</pre>
+<p>
+Such assignments are useless, and may indicate a logic error or typo.
+</p>
+
+    
+<h3><a name="SF_SWITCH_FALLTHROUGH">SF: Switch statement found where one case falls through to the next case (SF_SWITCH_FALLTHROUGH)</a></h3>
+
+
+  <p> This method contains a switch statement where one case branch will fall through to the next case.
+  Usually you need to end this case with a break or return.</p>
+
+    
+<h3><a name="SF_SWITCH_NO_DEFAULT">SF: Switch statement found where default case is missing (SF_SWITCH_NO_DEFAULT)</a></h3>
+
+
+  <p> This method contains a switch statement where default case is missing.
+  Usually you need to provide a default case.</p>
+
+    
+<h3><a name="ST_WRITE_TO_STATIC_FROM_INSTANCE_METHOD">ST: Write to static field from instance method (ST_WRITE_TO_STATIC_FROM_INSTANCE_METHOD)</a></h3>
+
+
+  <p> This instance method writes to a static field. This is tricky to get
+correct if multiple instances are being manipulated,
+and generally bad practice.
+</p>
+
+    
+<h3><a name="SE_PRIVATE_READ_RESOLVE_NOT_INHERITED">Se: private readResolve method not inherited by subclasses (SE_PRIVATE_READ_RESOLVE_NOT_INHERITED)</a></h3>
+
+
+  <p> This class defines a private readResolve method. Since it is private, it won't be inherited by subclasses.
+This might be intentional and OK, but should be reviewed to ensure it is what is intended.
+</p>
+
+    
+<h3><a name="SE_TRANSIENT_FIELD_OF_NONSERIALIZABLE_CLASS">Se: Transient field of class that isn't Serializable.  (SE_TRANSIENT_FIELD_OF_NONSERIALIZABLE_CLASS)</a></h3>
+
+
+  <p> The field is marked as transient, but the class isn't Serializable, so marking it as transient
+has absolutely no effect.
+This may be leftover marking from a previous version of the code in which the class was transient, or
+it may indicate a misunderstanding of how serialization works.
+</p>
+
+    
+<h3><a name="TQ_EXPLICIT_UNKNOWN_SOURCE_VALUE_REACHES_ALWAYS_SINK">TQ: Value required to have type qualifier, but marked as unknown (TQ_EXPLICIT_UNKNOWN_SOURCE_VALUE_REACHES_ALWAYS_SINK)</a></h3>
+
+      
+      <p>
+      A value is used in a way that requires it to be always be a value denoted by a type qualifier, but
+    there is an explicit annotation stating that it is not known where the value is required to have that type qualifier.
+    Either the usage or the annotation is incorrect.
+      </p>
+      
+    
+<h3><a name="TQ_EXPLICIT_UNKNOWN_SOURCE_VALUE_REACHES_NEVER_SINK">TQ: Value required to not have type qualifier, but marked as unknown (TQ_EXPLICIT_UNKNOWN_SOURCE_VALUE_REACHES_NEVER_SINK)</a></h3>
+
+      
+      <p>
+      A value is used in a way that requires it to be never be a value denoted by a type qualifier, but
+    there is an explicit annotation stating that it is not known where the value is prohibited from having that type qualifier.
+    Either the usage or the annotation is incorrect.
+      </p>
+      
+    
+<h3><a name="UCF_USELESS_CONTROL_FLOW">UCF: Useless control flow (UCF_USELESS_CONTROL_FLOW)</a></h3>
+
+
+<p> This method contains a useless control flow statement, where
+control flow continues onto the same place regardless of whether or not
+the branch is taken. For example,
+this is caused by having an empty statement
+block for an <code>if</code> statement:</p>
+<pre>
+    if (argv.length == 0) {
+    // TODO: handle this case
+    }
+</pre>
+
+    
+<h3><a name="UCF_USELESS_CONTROL_FLOW_NEXT_LINE">UCF: Useless control flow to next line (UCF_USELESS_CONTROL_FLOW_NEXT_LINE)</a></h3>
+
+
+<p> This method contains a useless control flow statement in which control
+flow follows to the same or following line regardless of whether or not
+the branch is taken.
+Often, this is caused by inadvertently using an empty statement as the
+body of an <code>if</code> statement, e.g.:</p>
+<pre>
+    if (argv.length == 1);
+        System.out.println("Hello, " + argv[0]);
+</pre>
+
+    
+<h3><a name="URF_UNREAD_PUBLIC_OR_PROTECTED_FIELD">UrF: Unread public/protected field (URF_UNREAD_PUBLIC_OR_PROTECTED_FIELD)</a></h3>
+
+
+  <p> This field is never read.&nbsp
+The field is public or protected, so perhaps
+    it is intended to be used with classes not seen as part of the analysis. If not,
+consider removing it from the class.</p>
+
+    
+<h3><a name="UUF_UNUSED_PUBLIC_OR_PROTECTED_FIELD">UuF: Unused public or protected field (UUF_UNUSED_PUBLIC_OR_PROTECTED_FIELD)</a></h3>
+
+
+  <p> This field is never used.&nbsp;
+The field is public or protected, so perhaps
+    it is intended to be used with classes not seen as part of the analysis. If not,
+consider removing it from the class.</p>
+
+    
+<h3><a name="UWF_FIELD_NOT_INITIALIZED_IN_CONSTRUCTOR">UwF: Field not initialized in constructor but dereferenced without null check (UWF_FIELD_NOT_INITIALIZED_IN_CONSTRUCTOR)</a></h3>
+
+
+  <p> This field is never initialized within any constructor, and is therefore could be null after
+the object is constructed. Elsewhere, it is loaded and dereferenced without a null check.
+This could be a either an error or a questionable design, since
+it means a null pointer exception will be generated if that field is dereferenced
+before being initialized.
+</p>
+
+    
+<h3><a name="UWF_UNWRITTEN_PUBLIC_OR_PROTECTED_FIELD">UwF: Unwritten public or protected field (UWF_UNWRITTEN_PUBLIC_OR_PROTECTED_FIELD)</a></h3>
+
+
+  <p> No writes were seen to this public/protected field.&nbsp; All reads of it will return the default
+value. Check for errors (should it have been initialized?), or remove it if it is useless.</p>
+
+    
+<h3><a name="XFB_XML_FACTORY_BYPASS">XFB: Method directly allocates a specific implementation of xml interfaces (XFB_XML_FACTORY_BYPASS)</a></h3>
+
+      
+      <p>
+      This method allocates a specific implementation of an xml interface. It is preferable to use
+      the supplied factory classes to create these objects so that the implementation can be
+      changed at runtime. See
+      </p>
+      <ul>
+         <li>javax.xml.parsers.DocumentBuilderFactory</li>
+         <li>javax.xml.parsers.SAXParserFactory</li>
+         <li>javax.xml.transform.TransformerFactory</li>
+         <li>org.w3c.dom.Document.create<i>XXXX</i></li>
+      </ul>
+      <p>for details.</p>
+      
+    
+
+
+<hr> <p> 
+<script language="JavaScript" type="text/javascript"> 
+<!---//hide script from old browsers 
+document.write( "Last updated "+ document.lastModified + "." ); 
+//end hiding contents ---> 
+</script> 
+<p> Send comments to <a class="sidebar" href="mailto:findbugs@cs.umd.edu">findbugs@cs.umd.edu</a> 
+<p> 
+<A href="http://sourceforge.net"><IMG src="http://sourceforge.net/sflogo.php?group_id=96405&amp;type=5" width="210" height="62" border="0" alt="SourceForge.net Logo" /></A>
+</td></tr></table>
+</body></html>
diff --git a/doc/bug-logo.png b/doc/bug-logo.png
new file mode 100644
index 0000000..8d719d0
--- /dev/null
+++ b/doc/bug-logo.png
Binary files differ
diff --git a/doc/bugDescriptions.html b/doc/bugDescriptions.html
new file mode 100644
index 0000000..a8f61c5
--- /dev/null
+++ b/doc/bugDescriptions.html
@@ -0,0 +1,5282 @@
+<html><head><title>FindBugs Bug Descriptions</title>
+<link rel="stylesheet" type="text/css" href="findbugs.css"/>
+<link rel="shortcut icon" href="favicon.ico" type="image/x-icon"/>
+</head><body>
+
+<table width="100%"><tr>
+
+<td bgcolor="#b9b9fe" valign="top" align="left" width="20%"> 
+<table width="100%" cellspacing="0" border="0"> 
+<tr><td><a class="sidebar" href="index.html"><img src="umdFindbugs.png" alt="FindBugs"></a></td></tr> 
+
+<tr><td>&nbsp;</td></tr>
+
+<tr><td><b>Docs and Info</b></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="findbugs2.html">FindBugs 2.0</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="demo.html">Demo and data</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="users.html">Users and supporters</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="http://findbugs.blogspot.com/">FindBugs blog</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="factSheet.html">Fact sheet</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="manual/index.html">Manual</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="ja/manual/index.html">Manual(ja/&#26085;&#26412;&#35486;)</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="FAQ.html">FAQ</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="bugDescriptions.html">Bug descriptions</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="mailingLists.html">Mailing lists</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="publications.html">Documents and Publications</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="links.html">Links</a></font></td></tr> 
+
+<tr><td>&nbsp;</td></tr>
+
+<tr><td><a class="sidebar" href="downloads.html"><b>Downloads</b></a></td></tr> 
+
+<tr><td>&nbsp;</td></tr>
+
+<tr><td><a class="sidebar" href="http://www.cafeshops.com/findbugs"><b>FindBugs Swag</b></a></td></tr>
+
+<tr><td>&nbsp;</td></tr>
+
+<tr><td><b>Development</b></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="http://sourceforge.net/tracker/?group_id=96405">Open bugs</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="reportingBugs.html">Reporting bugs</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="contributing.html">Contributing</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="team.html">Dev team</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="api/index.html">API</a> <a class="sidebar" href="api/overview-summary.html">[no frames]</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="Changes.html">Change log</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="http://sourceforge.net/projects/findbugs">SF project page</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="http://code.google.com/p/findbugs/source/browse/">Browse source</a></font></td></tr> 
+<tr><td><font size="-1"><a class="sidebar" href="http://code.google.com/p/findbugs/source/list">Latest code changes</a></font></td></tr> 
+</table> 
+</td>
+<td align="left" valign="top">
+<h1>FindBugs Bug Descriptions</h1>
+<p>This document lists the standard bug patterns reported by
+<a href="http://findbugs.sourceforge.net">FindBugs</a> version 2.0.1.</p>
+<h2>Summary</h2>
+<table width="100%">
+<tr bgcolor="#b9b9fe"><th>Description</th><th>Category</th></tr>
+<tr bgcolor="#eeeeee"><td><a href="#AM_CREATES_EMPTY_JAR_FILE_ENTRY">AM: Creates an empty jar file entry</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#AM_CREATES_EMPTY_ZIP_FILE_ENTRY">AM: Creates an empty zip file entry</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#BC_EQUALS_METHOD_SHOULD_WORK_FOR_ALL_OBJECTS">BC: Equals method should not assume anything about the type of its argument</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#BIT_SIGNED_CHECK">BIT: Check for sign of bitwise operation</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#CN_IDIOM">CN: Class implements Cloneable but does not define or use clone method</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#ffffff"><td><a href="#CN_IDIOM_NO_SUPER_CALL">CN: clone method does not call super.clone()</a></td><td>Bad practice</td></tr>
+<tr bgcolor="#eeeeee"><td><a href="#CN_IMPLEMENTS_CLONE_BUT_NOT_CLONEABLE">CN: Class defines clone() but doesn't implement Clonea