SpotBugs - Messages

Searching for all files in '/var/jenkins_home/jobs/SolidBlue3/workspace' that match the pattern '**/target/**/findbugsXml.xml,**/target/**/spotbugsXml.xml'
Traversing of symbolic links: enabled
-> found 4 files
Successfully parsed file /var/jenkins_home/jobs/SolidBlue3/workspace/target/solidblue3j/modules/solidblue3-application-nogui/spotbugsXml.xml
-> found 0 issues (skipped 0 duplicates)
Successfully processed file 'target/solidblue3j/modules/solidblue3-application-nogui/spotbugsXml.xml'
Successfully parsed file /var/jenkins_home/jobs/SolidBlue3/workspace/target/solidblue3j/modules/solidblue3-commons/spotbugsXml.xml
-> found 0 issues (skipped 0 duplicates)
Successfully processed file 'target/solidblue3j/modules/solidblue3-commons/spotbugsXml.xml'
Successfully parsed file /var/jenkins_home/jobs/SolidBlue3/workspace/target/solidblue3j/modules/solidblue3-dao/spotbugsXml.xml
-> found 1 issue (skipped 0 duplicates)
Successfully processed file 'target/solidblue3j/modules/solidblue3-dao/spotbugsXml.xml'
Successfully parsed file /var/jenkins_home/jobs/SolidBlue3/workspace/target/solidblue3j/modules/solidblue3-model/spotbugsXml.xml
-> found 0 issues (skipped 0 duplicates)
Successfully processed file 'target/solidblue3j/modules/solidblue3-model/spotbugsXml.xml'
Post processing issues on 'Master' 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 '/var/jenkins_home/jobs/SolidBlue3/workspace'
-> resolved paths in source directory (1 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 1 issues
Creating fingerprints for all affected code blocks to track issues over different builds
-> created fingerprints for 0 issues (skipped 1 issues)
Copying affected files to Jenkins' build folder '/var/jenkins_home/jobs/SolidBlue3/builds/21/files-with-issues'
-> 0 copied, 1 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
Obtaining reference build from same job (SolidBlue3 :: Archive)
Using reference build 'SolidBlue3 #19' to compute new, fixed, and outstanding issues
Issues delta (vs. reference build): outstanding: 1, new: 0, fixed: 0
No quality gates have been set - skipping
Health report is disabled - skipping
Created analysis result for 1 issues (found 0 new issues, fixed 0 issues)
Attaching ResultAction with ID 'spotbugs' to build 'SolidBlue3 #21'.