Index: doc/index.html |
diff --git a/doc/index.html b/doc/index.html |
index e89a7bcf10abba7ced2be430863a59520b91fbeb..111f6efddde68b10891ecb49badd69bbd0f204d1 100644 |
--- a/doc/index.html |
+++ b/doc/index.html |
@@ -77,27 +77,38 @@ |
a million times. |
</p> |
- <p>The current version of FindBugs is 2.0.1.</p> |
+ <p>The current version of FindBugs is 2.0.3.</p> |
<p> |
FindBugs requires JRE (or JDK) 1.5.0 or later to run. However, it can analyze programs |
- compiled for any version of Java, from 1.0 to 1.8. The current version of FindBugs is 2.0.1, |
- released on 19:56:04 EDT, 12 July, 2012. <a href="reportingBugs.html">We are very interested in getting |
+ compiled for any version of Java, from 1.0 to 1.7. Some classfiles compiled for Java 1.8 give |
+ FindBugs problems, the next major release of FindBugs will handle Java 1.8 classfiles. |
+ |
+ <p> The current version of FindBugs is 2.0.3, |
+ |
+ released on 17:16:15 EST, 22 November, 2013. <a href="reportingBugs.html">We are very interested in getting |
feedback on how to improve FindBugs</a>. File bug reports on <a |
href="http://sourceforge.net/tracker/?func=browse&group_id=96405&atid=614693"> our |
sourceforge bug tracker</a> |
</p> |
+ <p>The current version of FindBugs may encounter errors when analyzing |
+ Java 1.8 bytecode, due to changes in the classfile format. After FindBugs 2.0.3 |
+ is released, work will start on the next major release of FindBugs, which will |
+ be able to analyze Java 1.8 (and will require Java 1.7 to compile and run). |
+ |
<p> |
<a href="#changes">Changes</a> | <a href="#talks">Talks</a> | <a href="#papers">Papers </a> | <a |
href="#sponsors">Sponsors</a> | <a href="#support">Support</a> |
</p> |
- <h1>FindBugs 2.0 Release</h1> |
- <p>After many delays, we have released FindBugs 2.0. We are pretty happy and confident about the |
- functionality, although we know the documentation of the changes in 2.0 is lacking. We decided that |
- releasing 2.0 took precedence over fixing the documentation. Anyone currently using FindBugs 1.3.9 |
- should find FindBugs 2.0 to largely be a drop-in replacement that offers better accuracy and |
- performance.</p> |
+ |
+ <h1>FindBugs 2.0.3 Release</h1> |
+ <p>FindBugs 2.0.3 is intended to be a minor bug fix release over |
+ FindBugs 2.0.2. Although than some improvements to existing bug detectors |
+ and analysis engines, and a few new bug patterns, and some |
+ important bug fixes to the Eclipse plugin, no significant changes |
+ should be observed. Consult the <a href="Changes.html">Change log</a> |
+ for more details.</p> |
<p> |
Also check out <a href="http://code.google.com/p/findbugs/w/list">http://code.google.com/p/findbugs/w/list</a> |
@@ -106,13 +117,13 @@ |
<h3> |
- <a href="findbugs2.html">Major changes in FindBugs 2.0</a> |
+ <a href="findbugs2.html">Major changes in FindBugs 2.0 (from FindBugs 1.3.x)</a> |
</h3> |
<ul> |
<li><a href="findbugs2.html#cloud">FindBugs Communal cloud</a></li> |
<li><a href="findbugs2.html#updateChecks">checks for updated versions of FindBugs</a></li> |
<li><a href="findbugs2.html#plugins">Powerful plugin capabilities</a></li> |
- <li><a href="findbugs2.html#newBugPatterns">new bug patterns</a>, |
+ <li><a href="findbugs2.html#newBugPatterns">new bug patterns</a>, |
including new/improved support for <a href="findbugs2.html#guava">Guava</a> |
and <a href="findbugs2.html#jsr305">JSR-305</a> |
</li> |
@@ -146,18 +157,21 @@ |
<dd> |
<a href="http://kenai.com/projects/sqe/pages/Home">SQE: Software Quality Environment</a> |
</dd> |
+ <dt><a href="https://wiki.jenkins-ci.org/display/JENKINS">Jenkins</a></dt> |
+ <dd> <a href="https://wiki.jenkins-ci.org/display/JENKINS/FindBugs+Plugin">Jenkins FindBugs Plugin</a> |
+ |
<dt> |
<a href="http://wiki.hudson-ci.org/display/HUDSON/Home">Hudson</a> |
</dt> |
<dd> |
- <a href="http://wiki.hudson-ci.org/display/HUDSON/FindBugs+Plugin">http://wiki.hudson-ci.org/display/HUDSON/FindBugs+Plugin</a> |
+ <a href="http://wiki.hudson-ci.org/display/HUDSON/FindBugs+Plugin"> HUDSON FindBugs Plugin</a> |
</dd> |
<dt> |
<a href="http://www.jetbrains.com/idea/">IntelliJ</a> |
</dt> |
<dd> |
Several plugins, see <a href="http://code.google.com/p/findbugs/wiki/IntellijFindBugsPlugins">http://code.google.com/p/findbugs/wiki/IntellijFindBugsPlugins</a> |
- for a descrption. |
+ for a description. |
</dd> |
</dl> |
@@ -165,6 +179,17 @@ |
<h1>New</h1> |
<ul> |
+ |
+ <li>jFormatString library republished at |
+ <a href="http://code.google.com/p/j-format-string">http://code.google.com/p/j-format-string</a>. |
+ This is the library we use for compile time checking of format strings. It is separately published to |
+ |
+ <li>We're releasing FindBugs 2.0.3. |
+ |
+ Mostly small changes to address false positives, with one important fix to the Eclipse plugin |
+ to fix a problem that had prevented the plugin from running in some versions of Eclipse. |
+ Check the <a href="Changes.html">change log</a> for more details. |
+ |
<li>We've released <a href="findbugs2.html">FindBugs 2.0</a> |
</li> |
<li>FindBugs communal cloud and Java web start links:. We have analyzed several large open |
@@ -184,13 +209,14 @@ |
<h1>Experience with FindBugs</h1> |
+ <ul> |
<li><b>Google FindBugs Fixit</b>: Google has a tradition of <a |
href="http://www.nytimes.com/2007/10/21/jobs/21pre.html">engineering fixits</a>, special days where |
they try to get all of their engineers focused on some specific problem or technique for improving |
the systems at Google. A fixit might work to improve web accessibility, internal testing, removing |
TODO's from internal software, etc. |
- <p>On May 13-14, Google held a global fixit for UMD's FindBugs tool a static analysis tool for |
+ <p>In 2009, Google held a global fixit for UMD's FindBugs tool a static analysis tool for |
finding coding mistakes in Java software. The focus of the fixit was to get feedback on the |
4,000 highest confidence issues found by FindBugs at Google, and let Google engineers decide |
which issues, if any, needed fixing.</p> |
@@ -213,17 +239,20 @@ |
having to provide their own review first. These capabilities have all been contributed to UMD's |
open source FindBugs tool, although a fair bit of engineering remains to prepare the |
capabilities for general release and make sure they can integrate into systems outside of |
- Google. The new capabilities are expected to be ready for general release in Fall 2009.</p></li> |
- <ul></ul> |
+ Google. The new capabilities are expected to be ready for general release in Fall 2009.</p> |
+ </li> |
+ </ul> |
<h2> |
<a name="talks">Talks about FindBugs</a> |
</h2> |
<ul> |
- <p> |
+ <li> |
<a href="http://www.cs.umd.edu/~pugh/MistakesThatMatter.pdf">Mistakes That Matter</a>, JavaOne, |
2009 |
- </p> |
+ </li> |
+ <li><a href="http://youtu.be/jflQSFhYTEo?hd=1">Youtube video</a> showing of demo |
+ of our 2.0 Eclipse plugin (5 minutes)</li> |
<li><a href="http://findbugs.cs.umd.edu/talks/findbugs.mov">Quicktime movie</a> showing of demo |
of our new GUI to view some of the null pointer bugs in Eclipse (Big file warning: 23 Megabytes)</li> |
<li><a href="http://findbugs.cs.umd.edu/talks/JavaOne2007-TS2007.pdf">JavaOne 2007 talk on |
@@ -250,11 +279,11 @@ |
SIGPLAN-SIGSOFT Workshop on Program Analysis for Software Tools and Engineering</a>, June, 2007</li> |
<li><a href="http://findbugs.cs.umd.edu/papers/FindBugsExperiences07.pdf">Evaluating Static |
Analysis Defect Warnings On Production Software,</a> <a href="http://www.cs.umd.edu/~nat/">Nathaniel |
- Ayewah and <a href="http://www.cs.umd.edu/~pugh/">William Pugh</a>, Univ. of Maryland, and |
+ Ayewah</a> and <a href="http://www.cs.umd.edu/~pugh/">William Pugh</a>, Univ. of Maryland, and |
J. David Morgenthaler, John Penix and YuQian Zhou, Google, Inc., <a |
href="http://paste07.cs.washington.edu/">7th ACM SIGPLAN-SIGSOFT Workshop on Program |
Analysis for Software Tools and Engineering</a>, June, 2007 |
- </a></li> |
+ </li> |
</ul> |
<h1> |
@@ -265,8 +294,7 @@ |
href="http://www.cs.umd.edu/~pugh">Bill Pugh</a> and <a |
href="http://andrei.gmxhome.de/privat.html">Andrey Loskutov</a>. |
</p> |
- <p>Current funding for FindBugs comes from a Google Faculty Research Awards. We'd be interested in |
- any offers of support or sponsorship.</p> |
+ <p>The most recent funding for FindBugs comes from a Google Faculty Research Awards.</p> |
<h2> |
<a name="support">Additional Support</a> |
</h2> |
@@ -293,6 +321,7 @@ |
</p> |
<p>Any opinions, findings and conclusions or recommendations expressed in this material are those of |
the author(s) and do not necessarily reflect the views of the National Science Foundation (NSF). |
+ </p> |
<hr> <p> |
<script language="JavaScript" type="text/javascript"> |
@@ -302,7 +331,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&type=5" width="210" height="62" border="0" alt="SourceForge.net Logo" /></A></p> |
+<A href="http://sourceforge.net"><IMG src="http://sourceforge.net/sflogo.php?group_id=96405&type=5" width="210" height="62" border="0" alt="SourceForge.net Logo" /></A> |
</td> |
</tr> |
</table> |