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"
                     "../../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;">
 ]>
@@ skipping 26 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>3.0.0</edition>
+<edition>3.0.1</edition>
 
-<pubdate>20:25:27 CDT, 06 July, 2014</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 3.0.0 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-3.0.0.tar.gz?download">gzipped tar format</ulink> and
-<ulink url="http://prdownloads.sourceforge.net/findbugs/findbugs-3.0.0.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-3.0.0.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-3.0.0.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-3.0.0</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-3.0.0</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-3.0.0-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-3.0.0-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 1352 matching lines @@
       <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>
@@ skipping 58 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_3.0.0.20140706.zip?download"
->http://prdownloads.sourceforge.net/findbugs/edu.umd.cs.findbugs.plugin.eclipse_3.0.0.20140706.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_3.0.0.20140706/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 161 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>
@@ skipping 16 matching lines @@
     </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>
@@ skipping 1898 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>