Update findbugs from 3.0.0 to 3.0.1.

doc/reportingBugs.html

Index: doc/reportingBugs.html
diff --git a/doc/reportingBugs.html b/doc/reportingBugs.html
index 6ccb6008faedd8b31763ee5d30bc936399676fb0..b9f5f41794f10daddf3dd0ed33d1cd7fd2b840e9 100644
--- a/doc/reportingBugs.html
+++ b/doc/reportingBugs.html
@@ -42,7 +42,7 @@
 <tr><td>&nbsp;</td></tr>
 
 <tr><td><b>Development</b></td></tr> 
-<tr><td><font size="-1">&nbsp;<a class="sidebar" href="http://sourceforge.net/tracker/?group_id=96405">Open bugs</a></font></td></tr> 
+<tr><td><font size="-1">&nbsp;<a class="sidebar" href="http://sourceforge.net/p/findbugs/bugs/">Open bugs</a></font></td></tr> 
 <tr><td><font size="-1">&nbsp;<a class="sidebar" href="reportingBugs.html">Reporting bugs</a></font></td></tr> 
 <tr><td><font size="-1">&nbsp;<a class="sidebar" href="contributing.html">Contributing</a></font></td></tr> 
 <tr><td><font size="-1">&nbsp;<a class="sidebar" href="team.html">Dev team</a></font></td></tr> 
@@ -67,13 +67,13 @@ credit you on our website and in the manual.
 
 <p>
 Please report bugs using the
-<a href="http://sourceforge.net/tracker/?atid=614693&group_id=96405&func=browse">Sourceforge
+<a href="http://sourceforge.net/p/findbugs/_list/tickets?source=navbar">Sourceforge
 bugs tracker</a>.&nbsp; Note that you need to be logged in to sourceforge to
 use the bug tracker.
 </p>
 
 <p>
-If you cannot use the Sourceforge tracker, you can try sending 
+If you cannot use the Sourceforge tracker, you can try sending
 email to the <a href="http://www.cs.umd.edu/mailman/listinfo/findbugs-discuss"
 >findbugs-discuss mailing list</a>.&nbsp; You must be subscribed
 to the list to post a message.
@@ -84,14 +84,14 @@ Finally, as a last resort, you can email <a href="mailto:findbugs@cs.umd.edu">fi
 However, such emails are much less likely to be handled in a timely manner than
 posts to the tracker or mailing list.
 </p>
-	
+
 <h2>False and Inaccurate Warnings</h2>
-	
+
 <p>
-	Like most bug-detection tools based on static analysis, FindBugs
-	issues some warnings that do not correspond to real bugs.&nbsp;
-	While in general we would like to make the percentage of such warnings
-	small, we can never fully eliminate them.
+    Like most bug-detection tools based on static analysis, FindBugs
+    issues some warnings that do not correspond to real bugs.&nbsp;
+    While in general we would like to make the percentage of such warnings
+    small, we can never fully eliminate them.
 </p>
 
 <h2>Information to include</h2>
@@ -119,7 +119,7 @@ document.write( "Last updated "+ document.lastModified + "." );
 </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>
+<a href="http://sourceforge.net/projects/findbugs/"><img src="http://sourceforge.net/sflogo.php?group_id=96405&amp;type=5" width="210" height="62" border="0" alt="FindBugs on SourceForge.net" /></a>
 
 </td>