geoserver
1<!-- This file specifies a spotbugs filter for excluding reports that
2should not be considered errors.
3
4The format of this file is documented at:
5
6https://spotbugs.readthedocs.io/en/latest/filter.html
7
8When possible, please specify the full names of the bug codes,
9using the pattern attribute, to make it clearer what reports are
10being suppressed. You can find a listing of codes at:
11
12https://spotbugs.readthedocs.io/en/latest/bugDescriptions.html
13-->
14<FindBugsFilter>15<!-- Won't use prepared statements, very bad performance for geospatial use cases -->16<Match>17<Bug pattern="SQL_NONCONSTANT_STRING_PASSED_TO_EXECUTE"/>18</Match>19<Match>20<Bug pattern="SQL_PREPARED_STATEMENT_GENERATED_FROM_NONCONSTANT_STRING"/>21</Match>22<!-- Returns moslty false positives -->23<Match>24<Bug pattern="FE_FLOATING_POINT_EQUALITY"/>25</Match>26<!-- Too many cases where we have a semi-legit usage of same name -->27<Match>28<Bug pattern="NM_SAME_SIMPLE_NAME_AS_SUPERCLASS"/>29</Match>30<!-- False positives, might want to revisit later -->31<Match>32<Bug pattern="EC_UNRELATED_TYPES_USING_POINTER_EQUALITY"/>33</Match>34<!-- Annoying but not actually a bug per se, might want to revisit later -->35<Match>36<Bug pattern="MF_CLASS_MASKS_FIELD"/>37</Match>38<!-- False positives -->39<Match>40<Bug pattern="UWF_UNWRITTEN_FIELD"/>41</Match>42<!-- Too many false positives -->43<Match>44<Bug pattern="CN_IMPLEMENTS_CLONE_BUT_NOT_CLONEABLE"/>45</Match>46<!-- Too many false positives -->47<Match>48<Bug pattern="NP_NULL_ON_SOME_PATH_MIGHT_BE_INFEASIBLE"/>49</Match>50<!-- Too many false positives -->51<Match>52<Bug pattern="NP_BOOLEAN_RETURN_NULL"/>53</Match>54<!-- False positives under Java 11, see https://github.com/spotbugs/spotbugs/issues/87855and https://github.com/spotbugs/spotbugs/issues/756 -->
56<Match>57<Bug pattern="RCN_REDUNDANT_NULLCHECK_WOULD_HAVE_BEEN_A_NPE"/>58</Match>59</FindBugsFilter>60