During the Maven migration, the code scanner build plugin "SpotBugs" was not migrated. The plugin is to be reintegrated into the build process and a "selection" of reported problems are to be fixed.
See https://spotbugs.readthe docs.io/en/latest/maven.html
Tasks
- Define non-relevant bug categories
- Marking justified exceptions to rules. Adding exceptions via a comment was not standard, are there alternatives?
{{{
// IGNORE FindBugs(VO_VOLATILE_INCREMENT): Only "best effort" finding concurrent // modifications. modCount++; }}}
Test
At least in the Pom.xml of tl-parent-all there should now be a section for SpotBugs under plugins. SpotBugs should be executed when you run mvn clean verify, mvn clean install or their variants without clean in tl-parent-all. In addition, SpotBugs is now executed in Jekins with every build. Thanks to the newly installed "Warnings" plugin in Jenkins, the result can be viewed directly for each build. (To do this, click on "SpotBugs Warnings" in the left-hand column of a build)