Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(963)

Issues Search
    My Issues | Starred     Open | Closed | All

Side by Side Diff: doc/index.html

Issue 139673002: Updating Findbugs from 2.0.1 to 2.0.3 (Closed) Base URL: https://chromium.googlesource.com/chromium/deps/findbugs.git@master
Patch Set: bulach's nits Created 6 years, 11 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « doc/findbugs2.html ('k') | doc/ja/manual/building.html » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 <html> 1 <html>
2 <head> 2 <head>
3 <title>FindBugs&trade; - Find Bugs in Java Programs</title> 3 <title>FindBugs&trade; - Find Bugs in Java Programs</title>
4 <link rel="stylesheet" type="text/css" href="findbugs.css" /> 4 <link rel="stylesheet" type="text/css" href="findbugs.css" />
5 5
6 </head> 6 </head>
7 7
8 <body> 8 <body>
9 9
10 <table width="100%"> 10 <table width="100%">
(...skipping 59 matching lines...) Expand 10 before | Expand all | Expand 10 after
70 70
71 <p> 71 <p>
72 This is the web page for FindBugs, a program which uses stat ic analysis to look for bugs in Java 72 This is the web page for FindBugs, a program which uses stat ic analysis to look for bugs in Java
73 code.&nbsp; It is free software, distributed under the terms of the <a 73 code.&nbsp; It is free software, distributed under the terms of the <a
74 href="http://www.gnu.org/licenses/lgpl.html">Lesser GNU Public License</a>. The name 74 href="http://www.gnu.org/licenses/lgpl.html">Lesser GNU Public License</a>. The name
75 FindBugs&trade; and the <a href="buggy-sm.png">FindBugs logo </a> are trademarked by <a 75 FindBugs&trade; and the <a href="buggy-sm.png">FindBugs logo </a> are trademarked by <a
76 href="http://www.umd.edu">The University of Maryland</a> . FindBugs has been downloaded more than 76 href="http://www.umd.edu">The University of Maryland</a> . FindBugs has been downloaded more than
77 a million times. 77 a million times.
78 </p> 78 </p>
79 79
80 <p>The current version of FindBugs is 2.0.1.</p> 80 <p>The current version of FindBugs is 2.0.3.</p>
81 81
82 <p> 82 <p>
83 FindBugs requires JRE (or JDK) 1.5.0 or later to run.&nbsp; However, it can analyze programs 83 FindBugs requires JRE (or JDK) 1.5.0 or later to run.&nbsp; However, it can analyze programs
84 compiled for any version of Java, from 1.0 to 1.8. The curre nt version of FindBugs is 2.0.1, 84 compiled for any version of Java, from 1.0 to 1.7. Some clas sfiles compiled for Java 1.8 give
85 released on 19:56:04 EDT, 12 July, 2012. <a href="reportingB ugs.html">We are very interested in getting 85 FindBugs problems, the next major release of FindBugs will h andle Java 1.8 classfiles.
86
87 <p> The current version of FindBugs is 2.0.3,
88
89 released on 17:16:15 EST, 22 November, 2013. <a href="report ingBugs.html">We are very interested in getting
86 feedback on how to improve FindBugs</a>. File bug report s on <a 90 feedback on how to improve FindBugs</a>. File bug report s on <a
87 href="http://sourceforge.net/tracker/?func=browse&amp;gr oup_id=96405&amp;atid=614693"> our 91 href="http://sourceforge.net/tracker/?func=browse&amp;gr oup_id=96405&amp;atid=614693"> our
88 sourceforge bug tracker</a> 92 sourceforge bug tracker</a>
89 </p> 93 </p>
94 <p>The current version of FindBugs may encounter errors when ana lyzing
95 Java 1.8 bytecode, due to changes in the classfile format. After FindBugs 2.0.3
96 is released, work will start on the next major release of FindBu gs, which will
97 be able to analyze Java 1.8 (and will require Java 1.7 to compil e and run).
98
90 99
91 <p> 100 <p>
92 <a href="#changes">Changes</a> | <a href="#talks">Talks</a> | <a href="#papers">Papers </a> | <a 101 <a href="#changes">Changes</a> | <a href="#talks">Talks</a> | <a href="#papers">Papers </a> | <a
93 href="#sponsors">Sponsors</a> | <a href="#support">Suppo rt</a> 102 href="#sponsors">Sponsors</a> | <a href="#support">Suppo rt</a>
94 </p> 103 </p>
95 <h1>FindBugs 2.0 Release</h1> 104
96 <p>After many delays, we have released FindBugs 2.0. We are pret ty happy and confident about the 105 <h1>FindBugs 2.0.3 Release</h1>
97 functionality, although we know the documentation of the cha nges in 2.0 is lacking. We decided that 106 <p>FindBugs 2.0.3 is intended to be a minor bug fix release over
98 releasing 2.0 took precedence over fixing the documentation. Anyone currently using FindBugs 1.3.9 107 FindBugs 2.0.2. Although than some improvements to existing bug detectors
99 should find FindBugs 2.0 to largely be a drop-in replacement that offers better accuracy and 108 and analysis engines, and a few new bug patterns, and some
100 performance.</p> 109 important bug fixes to the Eclipse plugin, no significant change s
110 should be observed. Consult the <a href="Changes.html">Change lo g</a>
111 for more details.</p>
101 112
102 <p> 113 <p>
103 Also check out <a href="http://code.google.com/p/findbugs/w/ list">http://code.google.com/p/findbugs/w/list</a> 114 Also check out <a href="http://code.google.com/p/findbugs/w/ list">http://code.google.com/p/findbugs/w/list</a>
104 for more information about some recent features/changes in F indBugs. 115 for more information about some recent features/changes in F indBugs.
105 </p> 116 </p>
106 117
107 118
108 <h3> 119 <h3>
109 <a href="findbugs2.html">Major changes in FindBugs 2.0</a> 120 <a href="findbugs2.html">Major changes in FindBugs 2.0 (from FindBugs 1.3.x)</a>
110 </h3> 121 </h3>
111 <ul> 122 <ul>
112 <li><a href="findbugs2.html#cloud">FindBugs Communal cloud</ a></li> 123 <li><a href="findbugs2.html#cloud">FindBugs Communal cloud</ a></li>
113 <li><a href="findbugs2.html#updateChecks">checks for updated versions of FindBugs</a></li> 124 <li><a href="findbugs2.html#updateChecks">checks for updated versions of FindBugs</a></li>
114 <li><a href="findbugs2.html#plugins">Powerful plugin capabil ities</a></li> 125 <li><a href="findbugs2.html#plugins">Powerful plugin capabil ities</a></li>
115 <li><a href="findbugs2.html#newBugPatterns">new bug patterns </a>, 126 <li><a href="findbugs2.html#newBugPatterns">new bug patterns </a>,
116 including new/improved support for <a href="findbugs2.ht ml#guava">Guava</a> 127 including new/improved support for <a href="findbugs2.ht ml#guava">Guava</a>
117 and <a href="findbugs2.html#jsr305">JSR-305</a> 128 and <a href="findbugs2.html#jsr305">JSR-305</a>
118 </li> 129 </li>
119 <li><a href="findbugs2.html#performance">improved performanc e</a></li> 130 <li><a href="findbugs2.html#performance">improved performanc e</a></li>
120 </ul> 131 </ul>
121 132
122 133
123 <h2>Ways to run FindBugs</h2> 134 <h2>Ways to run FindBugs</h2>
124 <p>Here are various ways to run FindBugs. For plugins not suppor ted by the FindBugs team, check to 135 <p>Here are various ways to run FindBugs. For plugins not suppor ted by the FindBugs team, check to
125 see what version of FindBugs they provide; it might take a l ittle while for the plugins to update to 136 see what version of FindBugs they provide; it might take a l ittle while for the plugins to update to
(...skipping 13 matching lines...) Expand all
139 </dt> 150 </dt>
140 <dd> 151 <dd>
141 <a href="http://mojo.codehaus.org/findbugs-maven-plugin/ ">http://mojo.codehaus.org/findbugs-maven-plugin/</a> 152 <a href="http://mojo.codehaus.org/findbugs-maven-plugin/ ">http://mojo.codehaus.org/findbugs-maven-plugin/</a>
142 </dd> 153 </dd>
143 <dt> 154 <dt>
144 <a href="http://netbeans.org/">Netbeans</a> 155 <a href="http://netbeans.org/">Netbeans</a>
145 </dt> 156 </dt>
146 <dd> 157 <dd>
147 <a href="http://kenai.com/projects/sqe/pages/Home">SQE: Software Quality Environment</a> 158 <a href="http://kenai.com/projects/sqe/pages/Home">SQE: Software Quality Environment</a>
148 </dd> 159 </dd>
160 <dt><a href="https://wiki.jenkins-ci.org/display/JENKINS">Je nkins</a></dt>
161 <dd> <a href="https://wiki.jenkins-ci.org/display/JENKINS/Fi ndBugs+Plugin">Jenkins FindBugs Plugin</a>
162
149 <dt> 163 <dt>
150 <a href="http://wiki.hudson-ci.org/display/HUDSON/Home"> Hudson</a> 164 <a href="http://wiki.hudson-ci.org/display/HUDSON/Home"> Hudson</a>
151 </dt> 165 </dt>
152 <dd> 166 <dd>
153 <a href="http://wiki.hudson-ci.org/display/HUDSON/FindBu gs+Plugin">http://wiki.hudson-ci.org/display/HUDSON/FindBugs+Plugin</a> 167 <a href="http://wiki.hudson-ci.org/display/HUDSON/FindBu gs+Plugin"> HUDSON FindBugs Plugin</a>
154 </dd> 168 </dd>
155 <dt> 169 <dt>
156 <a href="http://www.jetbrains.com/idea/">IntelliJ</a> 170 <a href="http://www.jetbrains.com/idea/">IntelliJ</a>
157 </dt> 171 </dt>
158 <dd> 172 <dd>
159 Several plugins, see <a href="http://code.google.com/p/f indbugs/wiki/IntellijFindBugsPlugins">http://code.google.com/p/findbugs/wiki/Int ellijFindBugsPlugins</a> 173 Several plugins, see <a href="http://code.google.com/p/f indbugs/wiki/IntellijFindBugsPlugins">http://code.google.com/p/findbugs/wiki/Int ellijFindBugsPlugins</a>
160 for a descrption. 174 for a description.
161 175
162 </dd> 176 </dd>
163 </dl> 177 </dl>
164 178
165 179
166 <h1>New</h1> 180 <h1>New</h1>
167 <ul> 181 <ul>
182
183 <li>jFormatString library republished at
184 <a href="http://code.google.com/p/j-format-string">http://code.g oogle.com/p/j-format-string</a>.
185 This is the library we use for compile time checking of format s trings. It is separately published to
186
187 <li>We're releasing FindBugs 2.0.3.
188
189 Mostly small changes to address false positives, with one im portant fix to the Eclipse plugin
190 to fix a problem that had prevented the plugin from running in some versions of Eclipse.
191 Check the <a href="Changes.html">change log</a> for more details.
192
168 <li>We've released <a href="findbugs2.html">FindBugs 2.0</a> 193 <li>We've released <a href="findbugs2.html">FindBugs 2.0</a>
169 </li> 194 </li>
170 <li>FindBugs communal cloud and Java web start links:. We ha ve analyzed several large open 195 <li>FindBugs communal cloud and Java web start links:. We ha ve analyzed several large open
171 source projects, and provide Java web start links to all ow you to view the results. We'd be 196 source projects, and provide Java web start links to all ow you to view the results. We'd be
172 happy to work with projects to make the results availabl e from a continuous build: 197 happy to work with projects to make the results availabl e from a continuous build:
173 <p></p> 198 <p></p>
174 <ul> 199 <ul>
175 <li><a href="http://findbugs.cs.umd.edu/cloud/jdk.jn lp">Sun's JDK 8</a></li> 200 <li><a href="http://findbugs.cs.umd.edu/cloud/jdk.jn lp">Sun's JDK 8</a></li>
176 <li><a href="http://findbugs.cs.umd.edu/cloud/eclips e.jnlp">Eclipse 3.8</a></li> 201 <li><a href="http://findbugs.cs.umd.edu/cloud/eclips e.jnlp">Eclipse 3.8</a></li>
177 <li><a href="http://findbugs.cs.umd.edu/cloud/tomcat .jnlp">Apache Tomcat 7.0</a></li> 202 <li><a href="http://findbugs.cs.umd.edu/cloud/tomcat .jnlp">Apache Tomcat 7.0</a></li>
178 <li><a href="http://findbugs.cs.umd.edu/cloud/intell ij.jnlp">IntelliJ IDEA</a></li> 203 <li><a href="http://findbugs.cs.umd.edu/cloud/intell ij.jnlp">IntelliJ IDEA</a></li>
179 <li><a href="http://findbugs.cs.umd.edu/cloud/jboss. jnlp">JBoss</a></li> 204 <li><a href="http://findbugs.cs.umd.edu/cloud/jboss. jnlp">JBoss</a></li>
180 </ul> 205 </ul>
181 </li> 206 </li>
182 </ul> 207 </ul>
183 208
184 209
185 210
186 <h1>Experience with FindBugs</h1> 211 <h1>Experience with FindBugs</h1>
212 <ul>
187 <li><b>Google FindBugs Fixit</b>: Google has a tradition of <a 213 <li><b>Google FindBugs Fixit</b>: Google has a tradition of <a
188 href="http://www.nytimes.com/2007/10/21/jobs/21pre.html">eng ineering fixits</a>, special days where 214 href="http://www.nytimes.com/2007/10/21/jobs/21pre.html">eng ineering fixits</a>, special days where
189 they try to get all of their engineers focused on some speci fic problem or technique for improving 215 they try to get all of their engineers focused on some speci fic problem or technique for improving
190 the systems at Google. A fixit might work to improve web acc essibility, internal testing, removing 216 the systems at Google. A fixit might work to improve web acc essibility, internal testing, removing
191 TODO's from internal software, etc. 217 TODO's from internal software, etc.
192 218
193 <p>On May 13-14, Google held a global fixit for UMD's FindBu gs tool a static analysis tool for 219 <p>In 2009, Google held a global fixit for UMD's FindBugs to ol a static analysis tool for
194 finding coding mistakes in Java software. The focus of t he fixit was to get feedback on the 220 finding coding mistakes in Java software. The focus of t he fixit was to get feedback on the
195 4,000 highest confidence issues found by FindBugs at Goo gle, and let Google engineers decide 221 4,000 highest confidence issues found by FindBugs at Goo gle, and let Google engineers decide
196 which issues, if any, needed fixing.</p> 222 which issues, if any, needed fixing.</p>
197 <p>More than 700 engineers ran FindBugs from dozens of offic es. More than 250 of them entered 223 <p>More than 700 engineers ran FindBugs from dozens of offic es. More than 250 of them entered
198 more than 8,000 reviews of the issues. A review is a cla ssification of an issue as must-fix, 224 more than 8,000 reviews of the issues. A review is a cla ssification of an issue as must-fix,
199 should-fix, mostly-harmless, not-a-bug, and several othe r categories. More than 75% of the 225 should-fix, mostly-harmless, not-a-bug, and several othe r categories. More than 75% of the
200 reviews classified issues as must fix, should fix or I w ill fix. Many of the scariest issues 226 reviews classified issues as must fix, should fix or I w ill fix. Many of the scariest issues
201 received more than 10 reviews each.</p> 227 received more than 10 reviews each.</p>
202 <p>Engineers have already submitted changes that made more t han 1,100 of the 3,800 issues go 228 <p>Engineers have already submitted changes that made more t han 1,100 of the 3,800 issues go
203 away. Engineers filed more than 1,700 bug reports, of wh ich 600 have already been marked as 229 away. Engineers filed more than 1,700 bug reports, of wh ich 600 have already been marked as
204 fixed Work continues on addressing the issues raised by the fixit, and on supporting the 230 fixed Work continues on addressing the issues raised by the fixit, and on supporting the
205 integration of FindBugs into the software development pr ocess at Google.</p> 231 integration of FindBugs into the software development pr ocess at Google.</p>
206 <p>The fixit at Google showcased new capabilities of FindBug s that provide a cloud computing / 232 <p>The fixit at Google showcased new capabilities of FindBug s that provide a cloud computing /
207 social networking backdrop. Reviews of issues are immedi ately persisted into a central store, 233 social networking backdrop. Reviews of issues are immedi ately persisted into a central store,
208 where they can be seen by other developers, and FindBugs is integrated into the internal Google 234 where they can be seen by other developers, and FindBugs is integrated into the internal Google
209 tools for filing and viewing bug reports and for viewing the version control history of source 235 tools for filing and viewing bug reports and for viewing the version control history of source
210 files. For the Fixit, FindBugs was configured in a mode where engineers could not see reviews 236 files. For the Fixit, FindBugs was configured in a mode where engineers could not see reviews
211 from other engineers until they had entered their own; a fter the fixit, the configuration will 237 from other engineers until they had entered their own; a fter the fixit, the configuration will
212 be changed to a more open configuration where engineers can see reviews from others without 238 be changed to a more open configuration where engineers can see reviews from others without
213 having to provide their own review first. These capabili ties have all been contributed to UMD's 239 having to provide their own review first. These capabili ties have all been contributed to UMD's
214 open source FindBugs tool, although a fair bit of engine ering remains to prepare the 240 open source FindBugs tool, although a fair bit of engine ering remains to prepare the
215 capabilities for general release and make sure they can integrate into systems outside of 241 capabilities for general release and make sure they can integrate into systems outside of
216 Google. The new capabilities are expected to be ready fo r general release in Fall 2009.</p></li> 242 Google. The new capabilities are expected to be ready fo r general release in Fall 2009.</p>
217 <ul></ul> 243 </li>
244 </ul>
218 245
219 <h2> 246 <h2>
220 <a name="talks">Talks about FindBugs</a> 247 <a name="talks">Talks about FindBugs</a>
221 </h2> 248 </h2>
222 <ul> 249 <ul>
223 <p> 250 <li>
224 <a href="http://www.cs.umd.edu/~pugh/MistakesThatMatter. pdf">Mistakes That Matter</a>, JavaOne, 251 <a href="http://www.cs.umd.edu/~pugh/MistakesThatMatter. pdf">Mistakes That Matter</a>, JavaOne,
225 2009 252 2009
226 </p> 253 </li>
254 <li><a href="http://youtu.be/jflQSFhYTEo?hd=1">Youtube video </a> showing of demo
255 of our 2.0 Eclipse plugin (5 minutes)</li>
227 <li><a href="http://findbugs.cs.umd.edu/talks/findbugs.mov"> Quicktime movie</a> showing of demo 256 <li><a href="http://findbugs.cs.umd.edu/talks/findbugs.mov"> Quicktime movie</a> showing of demo
228 of our new GUI to view some of the null pointer bugs in Eclipse (Big file warning: 23 Megabytes)</li> 257 of our new GUI to view some of the null pointer bugs in Eclipse (Big file warning: 23 Megabytes)</li>
229 <li><a href="http://findbugs.cs.umd.edu/talks/JavaOne2007-TS 2007.pdf">JavaOne 2007 talk on 258 <li><a href="http://findbugs.cs.umd.edu/talks/JavaOne2007-TS 2007.pdf">JavaOne 2007 talk on
230 Improving Software Quality Using Static Analysis</a> </li> 259 Improving Software Quality Using Static Analysis</a> </li>
231 <li><a href="http://findbugs.cs.umd.edu/talks/fb-sdbp-2006.p df">Talk</a> Bill Pugh gave at <a 260 <li><a href="http://findbugs.cs.umd.edu/talks/fb-sdbp-2006.p df">Talk</a> Bill Pugh gave at <a
232 href="http://www.sdexpo.com/2006/sdbp/">SD Best Practice s</a>, Sept 14th (more of a handle on 261 href="http://www.sdexpo.com/2006/sdbp/">SD Best Practice s</a>, Sept 14th (more of a handle on
233 tutorial about using FindBugs)</li> 262 tutorial about using FindBugs)</li>
234 <li><a href="http://findbugs.cs.umd.edu/talks/fb-Sept1213-20 06.pdf">Talk</a> Bill Pugh gave at 263 <li><a href="http://findbugs.cs.umd.edu/talks/fb-Sept1213-20 06.pdf">Talk</a> Bill Pugh gave at
235 <a href="http://itasoftware.com/">ITA Software</a> and < a href="http://www.csail.mit.edu/">MIT</a>, 264 <a href="http://itasoftware.com/">ITA Software</a> and < a href="http://www.csail.mit.edu/">MIT</a>,
236 Sept 12th and 13th (more of a research focus)</li> 265 Sept 12th and 13th (more of a research focus)</li>
237 <li><a href="http://video.google.com/videoplay?docid=-815075 1070230264609">Video of talk</a> 266 <li><a href="http://video.google.com/videoplay?docid=-815075 1070230264609">Video of talk</a>
238 Bill Pugh gave at <a href="http://www.google.com">Google </a>, July 6th, 2006</li> 267 Bill Pugh gave at <a href="http://www.google.com">Google </a>, July 6th, 2006</li>
239 <li><a href="http://javaposse.com/index.php?post_id=95780">J ava Posse podcast interview 268 <li><a href="http://javaposse.com/index.php?post_id=95780">J ava Posse podcast interview
240 with Bill Pugh and Brian Goetz</a></li> 269 with Bill Pugh and Brian Goetz</a></li>
241 </ul> 270 </ul>
242 <h2> 271 <h2>
243 <a name="papers">Papers about FindBugs</a> 272 <a name="papers">Papers about FindBugs</a>
244 </h2> 273 </h2>
245 <ul> 274 <ul>
246 <li><a href="http://findbugs.cs.umd.edu/papers/MoreNullPoint erBugs07.pdf">Finding More Null 275 <li><a href="http://findbugs.cs.umd.edu/papers/MoreNullPoint erBugs07.pdf">Finding More Null
247 Pointer Bugs, But Not Too Many</a>, by <a href="http ://faculty.ycp.edu/~dhovemey/">David 276 Pointer Bugs, But Not Too Many</a>, by <a href="http ://faculty.ycp.edu/~dhovemey/">David
248 Hovemeyer</a>, York College of Pennsylvania and <a h ref="http://www.cs.umd.edu/~pugh/">William 277 Hovemeyer</a>, York College of Pennsylvania and <a h ref="http://www.cs.umd.edu/~pugh/">William
249 Pugh</a>, Univ. of Maryland, <a href="http://paste07 .cs.washington.edu/">7th ACM 278 Pugh</a>, Univ. of Maryland, <a href="http://paste07 .cs.washington.edu/">7th ACM
250 SIGPLAN-SIGSOFT Workshop on Program Analysis for Sof tware Tools and Engineering</a>, June, 2007</li> 279 SIGPLAN-SIGSOFT Workshop on Program Analysis for Sof tware Tools and Engineering</a>, June, 2007</li>
251 <li><a href="http://findbugs.cs.umd.edu/papers/FindBugsExper iences07.pdf">Evaluating Static 280 <li><a href="http://findbugs.cs.umd.edu/papers/FindBugsExper iences07.pdf">Evaluating Static
252 Analysis Defect Warnings On Production Software,</a> <a href="http://www.cs.umd.edu/~nat/">Nathaniel 281 Analysis Defect Warnings On Production Software,</a> <a href="http://www.cs.umd.edu/~nat/">Nathaniel
253 Ayewah and <a href="http://www.cs.umd.edu/~pugh/">Wi lliam Pugh</a>, Univ. of Maryland, and 282 Ayewah</a> and <a href="http://www.cs.umd.edu/~pugh/ ">William Pugh</a>, Univ. of Maryland, and
254 J. David Morgenthaler, John Penix and YuQian Zhou, G oogle, Inc., <a 283 J. David Morgenthaler, John Penix and YuQian Zhou, G oogle, Inc., <a
255 href="http://paste07.cs.washington.edu/">7th ACM SIG PLAN-SIGSOFT Workshop on Program 284 href="http://paste07.cs.washington.edu/">7th ACM SIG PLAN-SIGSOFT Workshop on Program
256 Analysis for Software Tools and Engineering</a>, June, 2007 285 Analysis for Software Tools and Engineering</a>, June, 2007
257 </a></li> 286 </li>
258 </ul> 287 </ul>
259 288
260 <h1> 289 <h1>
261 <a name="sponsors">Contributors and Sponsors</a> 290 <a name="sponsors">Contributors and Sponsors</a>
262 </h1> 291 </h1>
263 <p> 292 <p>
264 The <a href="team.html">current development team</a> consist s of <a 293 The <a href="team.html">current development team</a> consist s of <a
265 href="http://www.cs.umd.edu/~pugh">Bill Pugh</a> and <a 294 href="http://www.cs.umd.edu/~pugh">Bill Pugh</a> and <a
266 href="http://andrei.gmxhome.de/privat.html">Andrey Losku tov</a>. 295 href="http://andrei.gmxhome.de/privat.html">Andrey Losku tov</a>.
267 </p> 296 </p>
268 <p>Current funding for FindBugs comes from a Google Faculty Rese arch Awards. We'd be interested in 297 <p>The most recent funding for FindBugs comes from a Google Facu lty Research Awards.</p>
269 any offers of support or sponsorship.</p>
270 <h2> 298 <h2>
271 <a name="support">Additional Support</a> 299 <a name="support">Additional Support</a>
272 </h2> 300 </h2>
273 <p> 301 <p>
274 Numerous <a =href="team.html">people</a> have made significa nt contributions to the FindBugs 302 Numerous <a =href="team.html">people</a> have made significa nt contributions to the FindBugs
275 project, including founding work by <a href="http://goose.yc p.edu/~dhovemey/">David Hovemeyer</a> 303 project, including founding work by <a href="http://goose.yc p.edu/~dhovemey/">David Hovemeyer</a>
276 and the web cloud infrastructure by Keith Lea. 304 and the web cloud infrastructure by Keith Lea.
277 </p> 305 </p>
278 <p> 306 <p>
279 YourKit is kindly supporting open source projects with its f ull-featured Java Profiler. YourKit, LLC 307 YourKit is kindly supporting open source projects with its f ull-featured Java Profiler. YourKit, LLC
280 is creator of innovative and intelligent tools for profiling Java and .NET applications. Take a look 308 is creator of innovative and intelligent tools for profiling Java and .NET applications. Take a look
281 at YourKit's leading software products: <a href="http://www. yourkit.com/java/profiler/index.jsp">YourKit 309 at YourKit's leading software products: <a href="http://www. yourkit.com/java/profiler/index.jsp">YourKit
282 Java Profiler</a> and <a href="http://www.yourkit.com/.n et/profiler/index.jsp">YourKit .NET 310 Java Profiler</a> and <a href="http://www.yourkit.com/.n et/profiler/index.jsp">YourKit .NET
283 Profiler</a>. 311 Profiler</a>.
284 </p> 312 </p>
285 <p> 313 <p>
286 The FindBugs project also uses <a href="http://www.atlassian .com/software/fisheye/">FishEye</a> and 314 The FindBugs project also uses <a href="http://www.atlassian .com/software/fisheye/">FishEye</a> and
287 <a href="http://www.atlassian.com/software/clover/">Clover</ a>, which are generously provided by <a 315 <a href="http://www.atlassian.com/software/clover/">Clover</ a>, which are generously provided by <a
288 href="http://www.cenqua.com/">Cenqua/Atlassian</a>. 316 href="http://www.cenqua.com/">Cenqua/Atlassian</a>.
289 </p> 317 </p>
290 <p> 318 <p>
291 Additional financial support for the FindBugs project was pr ovided by <a href="http://www.nsf.gov">National 319 Additional financial support for the FindBugs project was pr ovided by <a href="http://www.nsf.gov">National
292 Science Foundation</a> grants ASC9720199 and CCR-0098162 , 320 Science Foundation</a> grants ASC9720199 and CCR-0098162 ,
293 </p> 321 </p>
294 <p>Any opinions, findings and conclusions or recommendations exp ressed in this material are those of 322 <p>Any opinions, findings and conclusions or recommendations exp ressed in this material are those of
295 the author(s) and do not necessarily reflect the views of th e National Science Foundation (NSF). 323 the author(s) and do not necessarily reflect the views of th e National Science Foundation (NSF).
324 </p>
296 325
297 <hr> <p> 326 <hr> <p>
298 <script language="JavaScript" type="text/javascript"> 327 <script language="JavaScript" type="text/javascript">
299 <!---//hide script from old browsers 328 <!---//hide script from old browsers
300 document.write( "Last updated "+ document.lastModified + "." ); 329 document.write( "Last updated "+ document.lastModified + "." );
301 //end hiding contents ---> 330 //end hiding contents --->
302 </script> 331 </script>
303 <p> Send comments to <a class="sidebar" href="mailto:findbugs@cs.umd.edu">findbu gs@cs.umd.edu</a> 332 <p> Send comments to <a class="sidebar" href="mailto:findbugs@cs.umd.edu">findbu gs@cs.umd.edu</a>
304 <p> 333 <p>
305 <A href="http://sourceforge.net"><IMG src="http://sourceforge.net/sflogo.php?gro up_id=96405&amp;type=5" width="210" height="62" border="0" alt="SourceForge.net Logo" /></A></p> 334 <A href="http://sourceforge.net"><IMG src="http://sourceforge.net/sflogo.php?gro up_id=96405&amp;type=5" width="210" height="62" border="0" alt="SourceForge.net Logo" /></A>
306 </td> 335 </td>
307 </tr> 336 </tr>
308 </table> 337 </table>
309 338
310 </body> 339 </body>
311 </html> 340 </html>
OLDNEW
« no previous file with comments | « doc/findbugs2.html ('k') | doc/ja/manual/building.html » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698