SpotBugs - Messages

Searching for all files in '/home/jenkins/agent/workspace/_and_Test_Pipeline_forked_master' that match the pattern '**/spotbugsXml.xml'
Traversing of symbolic links: enabled
-> found 4 files
Successfully parsed file /home/jenkins/agent/workspace/_and_Test_Pipeline_forked_master/modules/Example/target/site/spotbugsXml.xml
-> found 1 issue (skipped 0 duplicates)
Successfully processed file 'modules/Example/target/site/spotbugsXml.xml'
Successfully parsed file /home/jenkins/agent/workspace/_and_Test_Pipeline_forked_master/modules/MapView/target/site/spotbugsXml.xml
-> found 1 issue (skipped 0 duplicates)
Successfully processed file 'modules/MapView/target/site/spotbugsXml.xml'
Successfully parsed file /home/jenkins/agent/workspace/_and_Test_Pipeline_forked_master/target/mapview/it-tidalwave-mapview-modules/mapview-example/spotbugsXml.xml
-> found 1 issue (skipped 0 duplicates)
Successfully processed file 'target/mapview/it-tidalwave-mapview-modules/mapview-example/spotbugsXml.xml'
Successfully parsed file /home/jenkins/agent/workspace/_and_Test_Pipeline_forked_master/target/mapview/it-tidalwave-mapview-modules/mapview-javafx/spotbugsXml.xml
-> found 1 issue (skipped 0 duplicates)
Successfully processed file 'target/mapview/it-tidalwave-mapview-modules/mapview-javafx/spotbugsXml.xml'
Post processing issues on 'mapview-build-and-test-pipeline-forked-master-1-8ct72-5t2-pvq10' with source code encoding 'UTF-8'
Creating SCM blamer to obtain author and commit information for affected files
-> No blamer installed yet. You need to install the 'git-forensics' plugin to enable blaming for Git.
Resolving file names for all issues in workspace '/home/jenkins/agent/workspace/_and_Test_Pipeline_forked_master'
-> resolved paths in source directory (2 found, 0 not found)
Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)
-> all issues already have a valid module name
Resolving package names (or namespaces) by parsing the affected files
-> all affected files already have a valid package name
No filter has been set, publishing all 2 issues
Creating fingerprints for all affected code blocks to track issues over different builds
-> created fingerprints for 0 issues (skipped 2 issues)
Copying affected files to Jenkins' build folder '/var/jenkins_home/jobs/MapView_Build_and_Test_Pipeline_forked/branches/master/builds/1/files-with-issues'
-> 2 copied, 0 not in workspace, 0 not-found, 0 with I/O error
Repository miner is not configured, skipping repository mining
Reference build recorder is not configured
No valid reference build found
All reported issues will be considered outstanding
No quality gates have been set - skipping
Health report is disabled - skipping
Created analysis result for 2 issues (found 0 new issues, fixed 0 issues)
Attaching ResultAction with ID 'spotbugs' to build 'MapView_Build_and_Test_Pipeline_forked/master #1'.