SpotBugs - Messages

Searching for all files in '/var/jenkins_home/jobs/SolidBlue3_Metrics/workspace' that match the pattern '**/target/**/findbugsXml.xml,**/target/**/spotbugsXml.xml'
-> found 8 files
Successfully parsed file /var/jenkins_home/jobs/SolidBlue3_Metrics/workspace/modules/Application/target/site/spotbugsXml.xml
-> found 0 issues (skipped 0 duplicates)
Successfully parsed file /var/jenkins_home/jobs/SolidBlue3_Metrics/workspace/modules/Commons/target/site/spotbugsXml.xml
-> found 0 issues (skipped 0 duplicates)
Successfully parsed file /var/jenkins_home/jobs/SolidBlue3_Metrics/workspace/modules/Dao/target/site/spotbugsXml.xml
-> found 1 issue (skipped 0 duplicates)
Successfully parsed file /var/jenkins_home/jobs/SolidBlue3_Metrics/workspace/modules/Model/target/site/spotbugsXml.xml
-> found 0 issues (skipped 0 duplicates)
Successfully parsed file /var/jenkins_home/jobs/SolidBlue3_Metrics/workspace/target/solidblue3j/modules/solidblue3-application-nogui/spotbugsXml.xml
-> found 0 issues (skipped 0 duplicates)
Successfully parsed file /var/jenkins_home/jobs/SolidBlue3_Metrics/workspace/target/solidblue3j/modules/solidblue3-commons/spotbugsXml.xml
-> found 0 issues (skipped 0 duplicates)
Successfully parsed file /var/jenkins_home/jobs/SolidBlue3_Metrics/workspace/target/solidblue3j/modules/solidblue3-dao/spotbugsXml.xml
-> found 1 issue (skipped 0 duplicates)
Successfully parsed file /var/jenkins_home/jobs/SolidBlue3_Metrics/workspace/target/solidblue3j/modules/solidblue3-model/spotbugsXml.xml
-> found 0 issues (skipped 0 duplicates)
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_Metrics/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_Metrics/builds/29/files-with-issues'
-> 0 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
Obtaining reference build from same job (SolidBlue3 :: Metrics)
Using reference build 'SolidBlue3_Metrics #28' to compute new, fixed, and outstanding issues
Issues delta (vs. reference build): outstanding: 0, new: 1, fixed: 0
No quality gates have been set - skipping
Health report is disabled - skipping
Created analysis result for 1 issues (found 1 new issues, fixed 0 issues)
Attaching ResultAction with ID 'spotbugs' to build 'SolidBlue3_Metrics #29'.