Author: buildbot
Date: Wed Feb 25 14:10:09 2015
New Revision: 941454

Log:
Staging update by buildbot for sling

Modified:
    websites/staging/sling/trunk/content/   (props changed)
    websites/staging/sling/trunk/content/documentation/development/jsr-305.html

Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Feb 25 14:10:09 2015
@@ -1 +1 @@
-1662216
+1662217

Modified: 
websites/staging/sling/trunk/content/documentation/development/jsr-305.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/development/jsr-305.html 
(original)
+++ websites/staging/sling/trunk/content/documentation/development/jsr-305.html 
Wed Feb 25 14:10:09 2015
@@ -116,6 +116,7 @@ Also the annotations need to be configur
 <li>FindNullDeref</li>
 <li>FindNullDerefsInvolvingNonShortCircuitEvaluation</li>
 </ul>
+<p>A complete list of visitors class names in Findbugs can be found in the <a 
href="https://code.google.com/p/findbugs/source/browse/#git%2Ffindbugs%2Fsrc%2Fjava%2Fedu%2Fumd%2Fcs%2Ffindbugs%2Fdetect%253Fstate%253Dclosed";>sourcecode</a>.
 The according <a 
href="http://findbugs.sourceforge.net/bugDescriptions.html";>bug patterns</a> 
have an identifier (in parenthesis) for which you can search in the according 
Java classes, in case you want to extend the checks.</p>
 <p>Findbugs is also integrated in <a 
href="http://docs.sonarqube.org/display/SONAR/Findbugs+Plugin";>Sonarqube</a>.</p>
 <h2 id="use-with-maven">Use With Maven</h2>
 <p>You can also let Maven automatically run Findbugs to execute those checks 
via the <strong>findbugs-maven-plugin</strong>. For that just add the following 
plugin to your <code>pom.xml</code></p>
@@ -138,10 +139,9 @@ Also the annotations need to be configur
 </pre></div>
 
 
-<p>This example only runs those checks which are related to null checks. A 
complete list of visitors class names in Findbugs can be found in the <a 
href="https://code.google.com/p/findbugs/source/browse/#git%2Ffindbugs%2Fsrc%2Fjava%2Fedu%2Fumd%2Fcs%2Ffindbugs%2Fdetect%253Fstate%253Dclosed";>sourcecode</a>.
 The according <a 
href="http://findbugs.sourceforge.net/bugDescriptions.html";>bug patterns</a> 
have an identifier (in parenthesis) for which you can search in the according 
Java classes, in case you want to extend the checks.</p>
 <p>The results are often very imprecise (<a 
href="http://jira.codehaus.org/browse/MFINDBUGS-208";>MFINDBUGS-208</a>), 
especially when it comes to line numbers, therefore it is best to start the 
Findbugs GUI in case of errors found by this plugin via <code>mvn 
findbugs:gui</code>.</p>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; 
text-align: right;">
-        Rev. 1662216 by kwin on Wed, 25 Feb 2015 14:08:15 +0000
+        Rev. 1662217 by kwin on Wed, 25 Feb 2015 14:10:02 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Sling, Sling, Apache, the Apache feather logo, and the Apache 
Sling project


Reply via email to