Update findbugs from 3.0.0 to 3.0.1.

doc/manual.xml

 <?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
-                    "file:../etc/docbook/docbookx.dtd" [
+                    "../../etc/docbook/docbookx.dtd" [
 <!ENTITY FindBugs "<application>FindBugs</application>">
 <!ENTITY Ant "<application>Ant</application>">
 <!ENTITY Saxon "<application>Saxon</application>">
 <!ENTITY FBHome "<replaceable>$FINDBUGS_HOME</replaceable>">
 <!ENTITY FBHomeWin "<replaceable>&#x25;FINDBUGS_HOME&#x25;</replaceable>">
 <!ENTITY nbsp "&#160;">
 ]>
 
 <book lang="en" id="findbugs-manual">
 
@@ skipping 23 matching lines @@
 This manual is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License.
 To view a copy of this license, visit
 <ulink url="http://creativecommons.org/licenses/by-nc-sa/1.0/">http://creativecommons.org/licenses/by-nc-sa/1.0/</ulink>
 or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA.
 </para>
 <para>
 The name FindBugs and the FindBugs logo are trademarked by the University of Maryland.
 </para>
 </legalnotice>
 
-<edition>2.0.3</edition>
+<edition>3.0.1</edition>
 
-<pubdate>17:16:15 EST, 22 November, 2013</pubdate>
+<pubdate>12:37:51 EST, 06 March, 2015</pubdate>
 
 </bookinfo>
 
 <!--
    **************************************************************************
    Introduction
    **************************************************************************
 -->
 
 <chapter id="introduction">
 <title>Introduction</title>
 
 <para> &FindBugs;&trade; is a program to find bugs in Java programs.  It looks for instances
 of "bug patterns" --- code instances that are likely to be errors.</para>
 
-<para> This document describes version 2.0.3 of &FindBugs;.We
+<para> This document describes version 3.0.1 of &FindBugs;.We
 are very interested in getting your feedback on &FindBugs;. Please visit
 the <ulink url="http://findbugs.sourceforge.net">&FindBugs; web page</ulink> for
 the latest information on &FindBugs;, contact information, and support resources such
 as information about the &FindBugs; mailing lists.</para>
 
 <sect1>
 <title>Requirements</title>
 <para> To use &FindBugs;, you need a runtime environment compatible with
 <ulink url="http://java.sun.com/j2se">Java 2 Standard Edition</ulink>, version 1.5 or later.
 &FindBugs; is platform independent, and is known to run on GNU/Linux, Windows, and
@@ skipping 17 matching lines @@
 <para>
 This chapter explains how to install &FindBugs;.
 </para>
 
 <sect1>
 <title>Extracting the Distribution</title>
 
 <para>
 The easiest way to install &FindBugs; is to download a binary distribution.
 Binary distributions are available in
-<ulink url="http://prdownloads.sourceforge.net/findbugs/findbugs-2.0.3.tar.gz?download">gzipped tar format</ulink> and
-<ulink url="http://prdownloads.sourceforge.net/findbugs/findbugs-2.0.3.zip?download">zip format</ulink>.
+<ulink url="http://prdownloads.sourceforge.net/findbugs/findbugs-3.0.1.tar.gz?download">gzipped tar format</ulink> and
+<ulink url="http://prdownloads.sourceforge.net/findbugs/findbugs-3.0.1.zip?download">zip format</ulink>.
 Once you have downloaded a binary distribution, extract it into a directory of your choice.
 </para>
 
 <para>
 Extracting a gzipped tar format distribution:
 <screen>
-<prompt>$ </prompt><command>gunzip -c findbugs-2.0.3.tar.gz | tar xvf -</command>
+<prompt>$ </prompt><command>gunzip -c findbugs-3.0.1.tar.gz | tar xvf -</command>
 </screen>
 </para>
 
 <para>
 Extracting a zip format distribution:
 <screen>
-<prompt>C:\Software></prompt><command>unzip findbugs-2.0.3.zip</command>
+<prompt>C:\Software></prompt><command>unzip findbugs-3.0.1.zip</command>
 </screen>
 </para>
 
 <para>
 Usually, extracting a binary distribution will create a directory ending in
-<filename class="directory">findbugs-2.0.3</filename>. For example, if you extracted
+<filename class="directory">findbugs-3.0.1</filename>. For example, if you extracted
 the binary distribution from the <filename class="directory">C:\Software</filename>
 directory, then the &FindBugs; software will be extracted into the directory
-<filename class="directory">C:\Software\findbugs-2.0.3</filename>.
+<filename class="directory">C:\Software\findbugs-3.0.1</filename>.
 This directory is the &FindBugs; home directory.  We'll refer to it as
 &FBHome; (or &FBHomeWin; for Windows) throughout this manual.
 </para>
 </sect1>
 
 </chapter>
 
 <!--
    **************************************************************************
    Compiling FindBugs from Source
@@ skipping 10 matching lines @@
 </para>
 
 <sect1>
 <title>Prerequisites</title>
 
 <para>
 To compile &FindBugs; from source, you will need the following:
 <itemizedlist>
   <listitem>
     <para>
-      The <ulink url="http://prdownloads.sourceforge.net/findbugs/findbugs-2.0.3-source.zip?download"
+      The <ulink url="http://prdownloads.sourceforge.net/findbugs/findbugs-3.0.1-source.zip?download"
       >&FindBugs; source distribution</ulink>
     </para>
   </listitem>
   <listitem>
     <para>
       <ulink url="http://java.sun.com/j2se/">JDK 1.5.0 or later</ulink>
     </para>
   </listitem>
   <listitem>
     <para>
@@ skipping 42 matching lines @@
 
 </sect1>
 
 <sect1>
 <title>Extracting the Source Distribution</title>
 <para>
 After you download the source distribution, you'll need to extract it into
 a working directory.  A typical command to do this is:
 
 <screen>
-<prompt>$ </prompt><command>unzip findbugs-2.0.3-source.zip</command>
+<prompt>$ </prompt><command>unzip findbugs-3.0.1-source.zip</command>
 </screen>
 
 </para>
 </sect1>
 
 <sect1>
 <title>Modifying <filename>local.properties</filename></title>
 <para>
 If you intend to build the FindBugs documentation,
 you will need to modify the <filename>local.properties</filename> file
@@ skipping 700 matching lines @@
   <listitem>
     <para>
     Set the auxiliary classpath for analysis.  This classpath should include all
     jar files and directories containing classes that are part of the program
     being analyzed but you do not want to have analyzed for bugs.
     </para>
   </listitem>
   </varlistentry>
 
   <varlistentry>
+  <term><command>-auxclasspathFromInput</command> </term>
+  <listitem>
+    <para>
+    Read the auxiliary classpath for analysis from standard input, each line adds new
+    entry to the auxiliary classpath for analysis.
+    </para>
+  </listitem>
+  </varlistentry>
+
+  <varlistentry>
+  <term><command>-auxclasspathFromFile</command> <replaceable>filepath</replaceable></term>
+  <listitem>
+    <para>
+    Read the auxiliary classpath for analysis from file, each line adds new
+    entry to the auxiliary classpath for analysis.
+    </para>
+  </listitem>
+  </varlistentry>
+
+  <varlistentry>
+  <term><command>-analyzeFromFile</command> <replaceable>filepath</replaceable></term>
+  <listitem>
+    <para>
+    Read the files to analyze from file, each line adds new
+    entry to the classpath for analysis.
+    </para>
+  </listitem>
+  </varlistentry>
+
+  <varlistentry>
   <term><command>-userPrefs</command> <replaceable>edu.umd.cs.findbugs.core.prefs</replaceable></term>
   <listitem>
     <para>
     Set the path of the user preferences file to use, which might override some of the options abobe.
     Specifying <literal>userPrefs</literal> as first argument would mean some later
     options will override them, as last argument would mean they will override some previous options).
     This rationale behind this option is to reuse FindBugs Eclipse project settings for command
     line execution.
     </para>
   </listitem>
@@ skipping 457 matching lines @@
        without any package qualification.  By default, all detectors which are
        not disabled by default are run.
        </para>
     </listitem>
   </varlistentry>
 
   <varlistentry>
     <term><literal>omitVisitors</literal></term>
     <listitem>
        <para>
-       Optional attribute.  It is like the <literal>visitors</literal> attribute,
+       Optional attribute. It specifies a comma-separated list of bug detectors.
+       It is like the <literal>visitors</literal> attribute,
        except it specifies detectors which will <emphasis>not</emphasis> be run.
        </para>
     </listitem>
   </varlistentry>
 
   <varlistentry>
+    <term><literal>chooseVisitors</literal></term>
+    <listitem>
+       <para>
+       Optional attribute. It specifies a comma-separated list of bug detectors
+       prefixed with "+" or "-" to selectively enable/disable them.
+       </para>
+    </listitem>
+  </varlistentry>
+
+  <varlistentry>
     <term><literal>excludeFilter</literal></term>
     <listitem>
        <para>
        Optional attribute.  It specifies the filename of a filter specifying bugs
        to exclude from being reported.  See <xref linkend="filter" />.
        </para>
     </listitem>
   </varlistentry>
 
   <varlistentry>
@@ skipping 96 matching lines @@
           <para>
               Optional attribute. Set the path of the user preferences file to use, which might override some of the options abobe.
               Specifying <literal>userPreferencesFile</literal> as first argument would mean some later
               options will override them, as last argument would mean they will override some previous options).
               This rationale behind this option is to reuse FindBugs Eclipse project settings for command
               line execution.
             </para>
       </listitem>
   </varlistentry>
 
+  <varlistentry>
+      <term><literal>nested</literal></term>
+      <listitem>
+          <para>
+              Optional attribute which enables or disables scanning of nested jar and zip files found in
+                the list of files and directories to be analyzed.
+                By default, scanning of nested jar/zip files is enabled.
+          </para>
+      </listitem>
+  </varlistentry>
+
+  <varlistentry>
+    <term><literal>setExitCode</literal></term>
+    <listitem>
+       <para>
+       Optional boolean attribute.  Whether the exit code will be returned to
+       the main ant job. Defaults to "true".
+       </para>
+    </listitem>
+  </varlistentry>
+
 </variablelist>
 
 
 </para>
 
 <!--
 
 -->
 
 </sect1>
 
 </chapter>
 
 <!--
    **************************************************************************
    Using the FindBugs Eclipse plugin
    **************************************************************************
 -->
 
 <chapter id="eclipse">
 <title>Using the &FindBugs;&trade; Eclipse plugin</title>
 
 <para>
 The FindBugs Eclipse plugin allows &FindBugs; to be used within
 the <ulink url="http://www.eclipse.org/">Eclipse</ulink> IDE.
 The FindBugs Eclipse plugin was generously contributed by Peter Friese.
-Phil Crosby and Andrei Loskutov contributed major improvements
+Phil Crosby and Andrey Loskutov contributed major improvements
 to the plugin.
 </para>
 
 <sect1>
 <title>Requirements</title>
 
 <para>
 To use the &FindBugs; Plugin for Eclipse, you need Eclipse 3.3 or later,
 and JRE/JDK 1.5 or later.
 </para>
@@ skipping 31 matching lines @@
       <listitem>
         <para>
          Provides the daily build of FindBugs. No testing other than that it compiles.
         </para>
       </listitem>
     </varlistentry>
     </variablelist>
 
 <para>You can also manually
 download the plugin from the following link:
-<ulink url="http://prdownloads.sourceforge.net/findbugs/edu.umd.cs.findbugs.plugin.eclipse_2.0.3.20131122.zip?download"
->http://prdownloads.sourceforge.net/findbugs/edu.umd.cs.findbugs.plugin.eclipse_2.0.3.20131122.zip?download</ulink>.
+<ulink url="http://prdownloads.sourceforge.net/findbugs/edu.umd.cs.findbugs.plugin.eclipse_3.0.1.20150306.zip?download"
+>http://prdownloads.sourceforge.net/findbugs/edu.umd.cs.findbugs.plugin.eclipse_3.0.1.20150306.zip?download</ulink>.
 Extract it in Eclipse's "plugins" subdirectory.
-(So &lt;eclipse_install_dir&gt;/plugins/edu.umd.cs.findbugs.plugin.eclipse_2.0.3.20131122/findbugs.png
+(So &lt;eclipse_install_dir&gt;/plugins/edu.umd.cs.findbugs.plugin.eclipse_3.0.1.20150306/findbugs.png
 should be the path to the &FindBugs; logo.)
 
 </para>
 
 <para>
 Once the plugin is extracted, start Eclipse and choose
 <menuchoice>
   <guimenu>Help</guimenu>
   <guimenuitem>About Eclipse Platform</guimenuitem>
   <guimenuitem>Plug-in Details</guimenuitem>
@@ skipping 53 matching lines @@
     </para>
   </listitem>
 </itemizedlist>
 
 </sect1>
 
 <sect1>
 <title>Extending the Eclipse Plugin (since 2.0.0)</title>
 <para>
 Eclipse plugin supports contribution of custom &FindBugs; detectors (see also
-<ulink url="http://code.google.com/p/findbugs/source/browse/trunk/findbugs/src/doc/AddingDetectors.txt">AddingDetectors.txt</ulink>
+<ulink url="http://code.google.com/p/findbugs/source/browse/findbugs/src/doc/AddingDetectors.txt">AddingDetectors.txt</ulink>
 for more information). There are two ways to contribute custom plugins to the Eclipse:
 </para>
 <itemizedlist>
   <listitem>
     <para>
     Existing standard &FindBugs; detector packages can be configured via
     <menuchoice>
         <guimenu>Window</guimenu>
         <guimenuitem>Preferences</guimenuitem>
         <guimenuitem>Java</guimenuitem>
-        <guimenuitem>&FindBugs;</guimenuitem>
+        <guimenuitem>FindBugs</guimenuitem>
         <guimenuitem>Misc. Settings</guimenuitem>
         <guimenuitem>Custom Detectors</guimenuitem>
     </menuchoice>.
     Simply specify there locations of any additional plugin libraries.
     </para>
 
     <para>
     The benefit of this solution is that already existing detector packages can be
     used "as is", and that you can quickly verify the quality of third party detectors.
     The drawback is that you have to apply this settings in each
     new Eclipse workspace, and this settings can't be shared between team members.
     </para>
   </listitem>
 
   <listitem>
     <para>
     It is possible to contribute custom detectors via standard Eclipse extensions mechanism.
     </para>
 
     <para>
     Please check the documentation of the
-    <ulink url="http://code.google.com/p/findbugs/source/browse/trunk/eclipsePlugin/schema/detectorPlugins.exsd">
+    <ulink url="http://code.google.com/p/findbugs/source/browse/eclipsePlugin/schema/detectorPlugins.exsd">
     findBugsEclipsePlugin/schema/detectorPlugins.exsd</ulink>
     extension point how to update the plugin.xml. Existing &FindBugs; detector plugins can
     be easily "extended" to be full featured &FindBugs; AND 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.
     </para>
 
     <para>
     The benefit of this solution is that for given (shared) Eclipse installation
     each team member has exactly same detectors set, and there is no need to configure
     anything anymore. The (really small) precondition
     is that you have to convert your existing detectors package to the valid
     Eclipse plugin. You can do this even for third-party detector packages.
     Another major differentiator is the ability to extend the default FindBugs
     classpath at runtime with required third party libraries (see
-    <ulink url="http://code.google.com/p/findbugs/source/browse/trunk/findbugs/src/doc/AddingDetectors.txt">AddingDetectors.txt</ulink>
+    <ulink url="http://code.google.com/p/findbugs/source/browse/findbugs/src/doc/AddingDetectors.txt">AddingDetectors.txt</ulink>
     for more information).
     </para>
   </listitem>
 
 </itemizedlist>
 
 </sect1>
 
 <sect1>
 <title>Troubleshooting</title>
@@ skipping 38 matching lines @@
    Filter files
    **************************************************************************
 -->
 
 <chapter id="filter">
 <title>Filter Files</title>
 
 <para>
 Filter files may be used to include or exclude bug reports for particular classes
 and methods.  This chapter explains how to use filter files.
-
-<note>
-<title>Planned Features</title>
-<para>
-  Filters are currently only supported by the Command Line interface.
-  Eventually, filter support will be added to the GUI.
-</para>
-</note>
 </para>
 
 
 <sect1>
 <title>Introduction to Filter Files</title>
 
 <para>
 Conceptually, a filter matches bug instances against a set of criteria.
 By defining a filter, you can select bug instances for special treatment;
 for example, to exclude or include them in a report.
@@ skipping 102 matching lines @@
         </para>
     </listitem>
   </varlistentry>
 
  <varlistentry>
    <term><literal>&lt;Class&gt;</literal></term>
     <listitem>
         <para>
             This element matches warnings associated with a particular class. The
             <literal>name</literal> attribute is used to specify the exact or regex match pattern
-            for the class name.
+            for the class name.  The <literal>role</literal> attribute is the class role.
         </para>
 
         <para>
             As a backward compatibility measure, instead of element of this type, you can use
              <literal>class</literal> attribute on a <literal>Match</literal> element to specify
              exact an class name or <literal>classregex</literal> attribute to specify a regular
              expression to match the class name against.
         </para>
 
         <para>
             If the <literal>Match</literal> element contains neither a <literal>Class</literal> element,
             nor a <literal>class</literal> / <literal>classregex</literal> attribute, the predicate will apply
             to all classes. Such predicate is likely to match more bug instances than you want, unless it is
             refined further down with apropriate method or field predicates.
         </para>
     </listitem>
  </varlistentry>
 
  <varlistentry>
+   <term><literal>&lt;Source&gt;</literal></term>
+    <listitem>
+        <para>
+            This element matches warnings associated with a particular source file. The
+            <literal>name</literal> attribute is used to specify the exact or regex match pattern
+            for the source file name.
+        </para>
+    </listitem>
+ </varlistentry>
+
+ <varlistentry>
    <term><literal>&lt;Method&gt;</literal></term>
 
    <listitem><para>This element specifies a method.  The <literal>name</literal> is used to specify
    the exact or regex match pattern for the method name.
    The <literal>params</literal> attribute is a comma-separated list
    of the types of the method's parameters.  The <literal>returns</literal> attribute is
-   the method's return type.  In <literal>params</literal> and <literal>returns</literal>, class names
+   the method's return type. The <literal>role</literal> attribute is
+   the method role. In <literal>params</literal> and <literal>returns</literal>, class names
    must be fully qualified. (E.g., "java.lang.String" instead of just
    "String".) If one of the latter attributes is specified the other is required for creating a method signature.
    Note that you can provide either <literal>name</literal> attribute or <literal>params</literal>
    and <literal>returns</literal> attributes or all three of them. This way you can provide various kinds of
    name and signature based matches.
    </para></listitem>
  </varlistentry>
 
  <varlistentry>
    <term><literal>&lt;Field&gt;</literal></term>
 
    <listitem><para>This element specifies a field. The <literal>name</literal> attribute is is used to specify
    the exact or regex match pattern for the field name. You can also filter fields according to their signature -
    use <literal>type</literal> attribute to specify fully qualified type of the field. You can specify eiter or both
-   of these attributes in order to perform name / signature based matches.
+   of these attributes in order to perform name / signature based matches. The <literal>role</literal> attribute is
+   the field role.
    </para></listitem>
  </varlistentry>
 
    <varlistentry>
    <term><literal>&lt;Local&gt;</literal></term>
 
    <listitem><para>This element specifies a local variable. The <literal>name</literal> attribute is is used to specify
    the exact or regex match pattern for the local variable name. Local variables are variables defined within a method.
    </para></listitem>
  </varlistentry>
 
  <varlistentry>
    <term><literal>&lt;Or&gt;</literal></term>
     <listitem><para>
    This element combines <literal>Match</literal> clauses as disjuncts.  I.e., you can put two
    <literal>Method</literal> elements in an <literal>Or</literal> clause in order to match either method.
    </para></listitem>
  </varlistentry>
  <varlistentry>
    <term><literal>&lt;And&gt;</literal></term>
     <listitem><para>
    This element combines <literal>Match</literal> clauses which both must evaluate to true.  I.e., you can put
-   <literal>Bug</literal> and <literal>Priority</literal> elements in an <literal>And</literal> clause in order
-   to match specific bugs with given priority only.
+   <literal>Bug</literal> and <literal>Confidence</literal> elements in an <literal>And</literal> clause in order
+   to match specific bugs with given confidence only.
    </para></listitem>
  </varlistentry>
  <varlistentry>
    <term><literal>&lt;Not&gt;</literal></term>
     <listitem><para>
    This element inverts the included child <literal>Match</literal>. I.e., you can put a
    <literal>Bug</literal> element in a <literal>Not</literal> clause in order to match any bug
    excluding the given one.
    </para></listitem>
  </varlistentry>
 </variablelist>
 
 </sect1>
 
 <sect1>
 <title>Java element name matching</title>
 
 <para>
-If the <literal>name</literal> attribute of <literal>Class</literal>, <literal>Method</literal> or
-<literal>Field</literal> starts with the ~ character the rest of attribute content is interpreted as
+If the <literal>name</literal> attribute of <literal>Class</literal>, <literal>Source</literal>,
+<literal>Method</literal> or <literal>Field</literal> starts with the ~ character
+the rest of attribute content is interpreted as
 a Java regular expression that is matched against the names of the Java element in question.
 </para>
 
 <para>
 Note that the pattern is matched against whole element name and therefore .* clauses need to be used
 at pattern beginning and/or end to perform substring matching.
 </para>
 
 <para>
 See <ulink url="http://java.sun.com/j2se/1.5.0/docs/api/java/util/regex/Pattern.html"><literal>java.util.regex.Pattern</literal></ulink>
@@ skipping 221 matching lines @@
   <!-- test classes are suffixed by 'Test' -->
 
   <Not>
       <Bug code="IJU" /> <!-- 'IJU' is the code for bugs related to JUnit test code -->
   </Not>
 </Match>
 ]]>
 </programlisting>
 </para>
 
+<para>
+  12. Full exclusion filter file to match all classes generated from Groovy source files.
+
+<programlisting>
+<![CDATA[
+<?xml version="1.0" encoding="UTF-8"?>
+<FindBugsFilter>
+<Match>
+    <Source name="~.*\.groovy" />
+</Match>
+</FindBugsFilter>
+]]>
+</programlisting>
+</para>
+
 </sect1>
 
 <sect1>
 <title>Complete Example</title>
 
 <programlisting>
 <![CDATA[
 <FindBugsFilter>
      <Match>
        <Class name="com.foobar.ClassNotToBeAnalyzed" />
@@ skipping 182 matching lines @@
 &FindBugs; supports several annotations to express the developer's intent
 so that FindBugs can issue warnings more appropriately. You need to use
 Java 5 to use annotations, and must place the annotations.jar and jsr305.jar
 files in the classpath while compiling your program.
 </para>
 
 <variablelist>
   <varlistentry>
     <term><command>edu.umd.cs.findbugs.annotations.CheckForNull</command></term>
     <listitem>
-<command>[Target]</command> Field, Method, Parameter
+    <para>
+        <command>[Target]</command> Field, Method, Parameter
+    </para>
     </listitem>
     <listitem>
       <para>
 The annotated element might be null, and uses of the element should check for null.
 When this annotation is applied to a method it applies to the method return value.
       </para>
     </listitem>
   </varlistentry>
 
   <varlistentry>
     <term><command>edu.umd.cs.findbugs.annotations.CheckReturnValue</command></term>
     <listitem>
+    <para>
       <command>[Target]</command> Method, Constructor
+    </para>
     </listitem>
     <listitem>
       <variablelist>
         <varlistentry>
           <term><command>[Parameter]</command></term>
           <listitem>
             <para>
               <command>priority:</command>The priority of the warning (HIGH, MEDIUM, LOW, IGNORE). Default value:MEDIUM.
             </para>
           </listitem>
           <listitem>
             <para>
               <command>explanation:</command>A textual explaination of why the return value should be checked. Default value:"".
             </para>
           </listitem>
         </varlistentry>
       </variablelist>
     </listitem>
     <listitem>
       <para>
 This annotation is used to denote a method whose return value should always be checked after invoking the method.
       </para>
     </listitem>
   </varlistentry>
 
   <varlistentry>
     <term><command>edu.umd.cs.findbugs.annotations.DefaultAnnotation</command></term>
     <listitem>
-      <command>[Target]</command> Type, Package
+      <para>
+        <command>[Target]</command> Type, Package
+      </para>
     </listitem>
     <listitem>
       <variablelist>
         <varlistentry>
           <term><command>[Parameter]</command></term>
           <listitem>
             <para>
               <command>value:</command>Annotation class objects. More than one class can be specified.
             </para>
           </listitem>
@@ skipping 12 matching lines @@
 such as @NonNull, @CheckForNull, or @CheckReturnValue. In particular, you can use
 @DefaultAnnotation(NonNull.class) on a class or package, and then use @Nullable only
 on those parameters, methods or fields that you want to allow to be null.
       </para>
     </listitem>
   </varlistentry>
 
   <varlistentry>
     <term><command>edu.umd.cs.findbugs.annotations.DefaultAnnotationForFields</command></term>
     <listitem>
+    <para>
       <command>[Target]</command> Type, Package
+    </para>
     </listitem>
     <listitem>
       <variablelist>
         <varlistentry>
           <term><command>[Parameter]</command></term>
           <listitem>
             <para>
               <command>value:</command>Annotation class objects. More than one class can be specified.
             </para>
           </listitem>
           <listitem>
             <para>
               <command>priority:</command>Default priority(HIGH, MEDIUM, LOW, IGNORE). Default value:MEDIUM.
             </para>
           </listitem>
         </varlistentry>
       </variablelist>
     </listitem>
     <listitem>
       <para>
 This is same as the DefaultAnnotation except it only applys to fields.
       </para>
     </listitem>
   </varlistentry>
 
   <varlistentry>
     <term><command>edu.umd.cs.findbugs.annotations.DefaultAnnotationForMethods</command></term>
     <listitem>
+    <para>
       <command>[Target]</command> Type, Package
+    </para>
     </listitem>
     <listitem>
       <variablelist>
         <varlistentry>
           <term><command>[Parameter]</command></term>
           <listitem>
             <para>
               <command>value:</command>Annotation class objects. More than one class can be specified.
             </para>
           </listitem>
           <listitem>
             <para>
               <command>priority:</command>Default priority(HIGH, MEDIUM, LOW, IGNORE). Default value:MEDIUM.
             </para>
           </listitem>
         </varlistentry>
       </variablelist>
     </listitem>
     <listitem>
       <para>
 This is same as the DefaultAnnotation except it only applys to methods.
       </para>
     </listitem>
   </varlistentry>
 
   <varlistentry>
     <term><command>edu.umd.cs.findbugs.annotations.DefaultAnnotationForParameters</command></term>
     <listitem>
+    <para>
       <command>[Target]</command> Type, Package
+    </para>
     </listitem>
     <listitem>
       <variablelist>
         <varlistentry>
           <term><command>[Parameter]</command></term>
           <listitem>
             <para>
               <command>value:</command>Annotation class objects. More than one class can be specified.
             </para>
           </listitem>
           <listitem>
             <para>
               <command>priority:</command>Default priority(HIGH, MEDIUM, LOW, IGNORE). Default value:MEDIUM.
             </para>
           </listitem>
         </varlistentry>
       </variablelist>
     </listitem>
     <listitem>
       <para>
 This is same as the DefaultAnnotation except it only applys to method parameters.
       </para>
     </listitem>
   </varlistentry>
 
   <varlistentry>
     <term><command>edu.umd.cs.findbugs.annotations.NonNull</command></term>
     <listitem>
+    <para>
       <command>[Target]</command> Field, Method, Parameter
+    </para>
     </listitem>
     <listitem>
       <para>
 The annotated element must not be null.
 Annotated fields must not be null after construction has completed. Annotated methods must have non-null return values.
       </para>
     </listitem>
   </varlistentry>
 
   <varlistentry>
     <term><command>edu.umd.cs.findbugs.annotations.Nullable</command></term>
     <listitem>
+    <para>
       <command>[Target]</command> Field, Method, Parameter
+    </para>
     </listitem>
     <listitem>
       <para>
 The annotated element could be null under some circumstances. In general, this means
 developers will have to read the documentation to determine when a null value is
 acceptable and whether it is neccessary to check for a null value.  FindBugs will
 treat the annotated items as though they had no annotation.
       </para>
       <para>
-In pratice this annotation is useful only for overriding an overarching NonNull
+In practice this annotation is useful only for overriding an overarching NonNull
 annotation.
       </para>
     </listitem>
   </varlistentry>
 
   <varlistentry>
     <term><command>edu.umd.cs.findbugs.annotations.OverrideMustInvoke</command></term>
     <listitem>
+    <para>
       <command>[Target]</command> Method
+    </para>
     </listitem>
     <listitem>
       <variablelist>
         <varlistentry>
           <term><command>[Parameter]</command></term>
           <listitem>
             <para>
               <command>value:</command>Specify when the super invocation should be
               performed (FIRST, ANYTIME, LAST). Default value:ANYTIME.
             </para>
@@ skipping 17 matching lines @@
     <listitem>
       <para>
 This annotation is deprecated. Use CheckForNull instead.
       </para>
     </listitem>
   </varlistentry>
 
   <varlistentry>
     <term><command>edu.umd.cs.findbugs.annotations.SuppressWarnings</command></term>
     <listitem>
+    <para>
       <command>[Target]</command> Type, Field, Method, Parameter, Constructor, Package
+    </para>
     </listitem>
     <listitem>
       <variablelist>
         <varlistentry>
           <term><command>[Parameter]</command></term>
           <listitem>
             <para>
               <command>value:</command>The name of the warning. More than one name can be specified.
             </para>
           </listitem>
@@ skipping 14 matching lines @@
 warning if an annotation contains an unrecognized warning name. Compiler vendors should
 document the warning names they support in conjunction with this annotation type. They
 are encouraged to cooperate to ensure that the same names work across multiple compilers.
       </para>
     </listitem>
   </varlistentry>
 
   <varlistentry>
     <term><command>edu.umd.cs.findbugs.annotations.UnknownNullness</command></term>
     <listitem>
+    <para>
       <command>[Target]</command> Field, Method, Parameter
+    </para>
     </listitem>
     <listitem>
       <para>
 Used to indicate that the nullness of the target is unknown, or my vary in unknown ways in subclasses.
       </para>
     </listitem>
   </varlistentry>
 
   <varlistentry>
     <term><command>edu.umd.cs.findbugs.annotations.UnknownNullness</command></term>
     <listitem>
+    <para>
       <command>[Target]</command> Field, Method, Parameter
+    </para>
     </listitem>
     <listitem>
       <para>
 Used to indicate that the nullness of the target is unknown, or my vary in unknown ways in subclasses.
       </para>
     </listitem>
   </varlistentry>
 </variablelist>
 
 <para>
  &FindBugs; also supports the following annotations:
 <itemizedlist>
-  <listitem>net.jcip.annotations.GuardedBy</listitem>
-  <listitem>net.jcip.annotations.Immutable</listitem>
-  <listitem>net.jcip.annotations.NotThreadSafe</listitem>
-  <listitem>net.jcip.annotations.ThreadSafe</listitem>
+  <listitem><para>net.jcip.annotations.GuardedBy</para></listitem>
+  <listitem><para>net.jcip.annotations.Immutable</para></listitem>
+  <listitem><para>net.jcip.annotations.NotThreadSafe</para></listitem>
+  <listitem><para>net.jcip.annotations.ThreadSafe</para></listitem>
 </itemizedlist>
 </para>
 <para>
 You can refer the JCIP annotation <ulink url="http://jcip.net/annotations/doc/index.html">
 API documentation</ulink> at <ulink url="http://jcip.net/">Java Concurrency in Practice</ulink>.
 </para>
 </chapter>
 
 <!--
    **************************************************************************
@@ skipping 989 matching lines @@
 <para>Phil Crosby enhanced the Eclipse plugin to add a view
 to display the bug details.</para>
 
 <para>Dave Brosius fixed a number of bugs, added user preferences
 to the Swing GUI, improved several bug detectors, and
 contributed the string concatenation detector.</para>
 
 <para>Thomas Klaeger contributed a number of bug fixes and
 bug detector improvements.</para>
 
-<para>Andrei Loskutov made a number of improvements to the
-Eclipse plugin.</para>
+<para>Andrey Loskutov made a number of bug fixes and
+bug detector improvements. He is maintainer of the Eclipse plugin.</para>
 
 <para>Brian Goetz contributed a major refactoring of the
 visitor classes to improve readability and understandability.</para>
 
 <para> Pete Angstadt fixed several problems in the Swing GUI.</para>
 
 <para>Francis Lalonde provided a task resource file for the
 FindBugs Ant task.</para>
 
 <para>Garvin LeClaire contributed support for output in
@@ skipping 64 matching lines @@
 in the Ant task.</para>
 
 <para>Peter Hendriks extended the Eclipse plugin preferences,
 and fixed a bug related to renaming the Eclipse plugin ID.</para>
 
 <para>Mark McKay contributed an Ant task to launch the findbugs frame.</para>
 
 <para>Dieter von Holten (dvholten) contributed
 some German improvements to findbugs_de.properties.</para>
 
+<para>Kevin Lubick contributed fixes and tests for multi-quick-fixes and customizable
+annotation colors for Eclipse plugin.</para>
+
+<para>Tagir Valeev contributed several new bug detectors and improved existing ones.</para>
 
 <para>If you have contributed to &FindBugs;, but aren't mentioned above,
 please send email to <email>findbugs@cs.umd.edu</email> (and also accept
 our humble apologies).</para>
 
 </sect1>
 
 <sect1>
 <title>Software Used</title>
 
@@ skipping 116 matching lines @@
 </blockquote>
 
 </sect2>
 
 </sect1>
 
 </chapter>
 
 
 </book>