SpotBugs - Messages

Searching for all files in '/home/jenkins/agent/workspace/saaj-ri-master-build' that match the pattern '**/spotbugsXml.xml'
Traversing of symbolic links: enabled
-> found 1 file
Successfully parsed file /home/jenkins/agent/workspace/saaj-ri-master-build/saaj-ri/target/spotbugsXml.xml
-> found 339 issues (skipped 2 duplicates)
Successfully processed file 'saaj-ri/target/spotbugsXml.xml'
Post processing issues on 'basic-gr25s' 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/saaj-ri-master-build'
-> resolved paths in source directory (63 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 339 issues
Creating fingerprints for all affected code blocks to track issues over different builds
-> created fingerprints for 0 issues (skipped 339 issues)
Searching for all files in '/home/jenkins/agent/workspace/saaj-ri-master-build' that match the pattern '**/spotbugsXml.xml'
Traversing of symbolic links: enabled
-> found 1 file
Successfully parsed file /home/jenkins/agent/workspace/saaj-ri-master-build/saaj-ri/target/spotbugsXml.xml
-> found 339 issues (skipped 2 duplicates)
Successfully processed file 'saaj-ri/target/spotbugsXml.xml'
Post processing issues on 'basic-gr25s' 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/saaj-ri-master-build'
-> resolved paths in source directory (63 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 339 issues
Creating fingerprints for all affected code blocks to track issues over different builds
-> created fingerprints for 0 issues (skipped 339 issues)
Copying affected files to Jenkins' build folder '/var/jenkins/jobs/saaj-ri-master-build/builds/104/files-with-issues'
-> 63 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 (SAAJ RI master build)
Using reference build 'saaj-ri-master-build #103' to compute new, fixed, and outstanding issues
Issues delta (vs. reference build): outstanding: 339, new: 0, fixed: 0
No quality gates have been set - skipping
Health report is disabled - skipping
Created analysis result for 339 issues (found 0 new issues, fixed 0 issues)
Attaching ResultAction with ID 'spotbugs' to build 'saaj-ri-master-build #104'.