Author: kwin Date: Wed Feb 25 14:08:15 2015 New Revision: 1662216 URL: http://svn.apache.org/r1662216 Log: extends JSR 305 documentation (with maven-findbugs-plugin limitations)
Modified: sling/site/trunk/content/documentation/development/jsr-305.mdtext Modified: sling/site/trunk/content/documentation/development/jsr-305.mdtext URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/jsr-305.mdtext?rev=1662216&r1=1662215&r2=1662216&view=diff ============================================================================== --- sling/site/trunk/content/documentation/development/jsr-305.mdtext (original) +++ sling/site/trunk/content/documentation/development/jsr-305.mdtext Wed Feb 25 14:08:15 2015 @@ -52,4 +52,8 @@ You can also let Maven automatically run </goals> </execution> </executions> - </plugin> \ No newline at end of file + </plugin> + +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 [sourcecode](https://code.google.com/p/findbugs/source/browse/#git%2Ffindbugs%2Fsrc%2Fjava%2Fedu%2Fumd%2Fcs%2Ffindbugs%2Fdetect%253Fstate%253Dclosed). The according [bug patterns](http://findbugs.sourceforge.net/bugDescriptions.html) have an identifier (in parenthesis) for which you can search in the according Java classes, in case you want to extend the checks. + +The results are often very imprecise ([MFINDBUGS-208](http://jira.codehaus.org/browse/MFINDBUGS-208)), 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 `mvn findbugs:gui`. \ No newline at end of file