<commit_before><html>
	<head>
		<title>FindBugs&trade; - Find Bugs in Java Programs</title>
		<link rel="stylesheet" type="text/css" href="findbugs.css" />
		@GOOGLE_ANALYTICS@
	</head>

	<body>

		<table width="100%">
			<tr>

				@HTML_SIDEBAR@

				<td align="left" valign="top">

					<p>
					<table><tr>
					<td valign="center">
						<a href="@WEBSITE@/"><img src="buggy-sm.png"
								alt="FindBugs logo" border="0" /> </a>
					<td valign="center">	<a href="http://www.umd.edu/"><img src="informal.png"
								alt="UMD logo" border="0" /> </a>
					</tr></table>

					<h1>
						FindBugs&trade; - Find Bugs in Java Programs
					</h1>

					<p>
						This is the web page for FindBugs, a program which uses static analysis
						to  look for bugs
						in Java code.&nbsp; It is free software, distributed under the
						terms of the
						<a href="http://www.gnu.org/licenses/lgpl.html">Lesser GNU
							Public License</a>. The name FindBugs&trade; and the
						<a href="buggy-sm.png">FindBugs logo</a> are trademarked by
						<a href="http://www.umd.edu">The University of Maryland</a>.
						As of July, 2008, FindBugs has been downloaded more than 700,000 times. 
							</p>
					
				
								<p>
						FindBugs requires JRE (or JDK) 1.5.0 or later to run.&nbsp;
						However, it can analyze programs compiled for any version of Java.
						The current version of FindBugs is @VERSION@, released on
						@RELEASE_DATE@.
						<a href="reportingBugs.html">We are very interested in getting feedback on how to improve
						FindBugs</a>.
					</p>

					<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>New</h1>

<ul>
<li><p><b>JavaOne talk</b>: 
					<a href="http://www.cs.umd.edu/~pugh/MistakesThatMatter.pdf">Slides</a> from my JavaOne talk, 
					Mistakes That Matter.
					<li><p><b>FindBugs community review</b>: We are previewing <a href="communityReview.html">FindBugs community review</a>, 
					in which anyone can review issues in open source projects (i.e., mark
					issues as "must fix" or "mostly harmless"), and those reviews
					are automatically shared with other reviewers.
					<p>This is a pre-beta release, not ready for deployment. The implementation
					will be undergoing significant changes before general availability. 
					<p>Initially, we are posting results for 
					<a href="http://findbugs.cs.umd.edu/cloud/jdk7/index.jnlp">Sun's JDK 7</a> and 
					<a href="http://findbugs.cs.umd.edu/cloud/eclipse3.5/index.jnlp">Eclipse 3.5</a>
					
					
<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 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.<commit_msg>fix URL's for jnlp files<commit_after><html>
	<head>
		<title>FindBugs&trade; - Find Bugs in Java Programs</title>
		<link rel="stylesheet" type="text/css" href="findbugs.css" />
		@GOOGLE_ANALYTICS@
	</head>

	<body>

		<table width="100%">
			<tr>

				@HTML_SIDEBAR@

				<td align="left" valign="top">

					<p>
					<table><tr>
					<td valign="center">
						<a href="@WEBSITE@/"><img src="buggy-sm.png"
								alt="FindBugs logo" border="0" /> </a>
					<td valign="center">	<a href="http://www.umd.edu/"><img src="informal.png"
								alt="UMD logo" border="0" /> </a>
					</tr></table>

					<h1>
						FindBugs&trade; - Find Bugs in Java Programs
					</h1>

					<p>
						This is the web page for FindBugs, a program which uses static analysis
						to  look for bugs
						in Java code.&nbsp; It is free software, distributed under the
						terms of the
						<a href="http://www.gnu.org/licenses/lgpl.html">Lesser GNU
							Public License</a>. The name FindBugs&trade; and the
						<a href="buggy-sm.png">FindBugs logo</a> are trademarked by
						<a href="http://www.umd.edu">The University of Maryland</a>.
						As of July, 2008, FindBugs has been downloaded more than 700,000 times. 
							</p>
					
				
								<p>
						FindBugs requires JRE (or JDK) 1.5.0 or later to run.&nbsp;
						However, it can analyze programs compiled for any version of Java.
						The current version of FindBugs is @VERSION@, released on
						@RELEASE_DATE@.
						<a href="reportingBugs.html">We are very interested in getting feedback on how to improve
						FindBugs</a>.
					</p>

					<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>New</h1>

<ul>
<li><p><b>JavaOne talk</b>: 
					<a href="http://www.cs.umd.edu/~pugh/MistakesThatMatter.pdf">Slides</a> from my JavaOne talk, 
					Mistakes That Matter.
					<li><p><b>FindBugs community review</b>: We are previewing <a href="communityReview.html">FindBugs community review</a>, 
					in which anyone can review issues in open source projects (i.e., mark
					issues as "must fix" or "mostly harmless"), and those reviews
					are automatically shared with other reviewers.
					<p>This is a pre-beta release, not ready for deployment. The implementation
					will be undergoing significant changes before general availability. 
					<p>Initially, we are posting results for:
					<ul>
					<li>
					<a href="http://findbugs.cs.umd.edu/cloud/jdk7.jnlp">Sun's JDK 7</a>  
					<li>
					<a href="http://findbugs.cs.umd.edu/cloud/eclipse.jnlp">Eclipse 3.5</a>
					</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 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.
{'fraction_non_alphanumeric': 0.12954279015240328, 'fraction_numerical': 0.013188745603751465, 'mean_word_length': 3.0241745283018866, 'pattern_counts': {'":': 0, '<': 159, '<?xml version=': 0, '>': 159, 'https://': 0, 'lorem ipsum': 0, 'www.': 10, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5187571', 'n_tokens_mistral': 2854, 'n_tokens_neox': 2166, 'n_words': 734}