JavaDoc - Messages

Successfully parsed console log
-> found 15 issues (skipped 15 duplicates)
Successfully parsed console log
-> found 15 issues (skipped 15 duplicates)
Successfully parsed console log
-> found 15 issues (skipped 15 duplicates)
Successfully parsed console log
-> found 15 issues (skipped 15 duplicates)
Parsing console log (workspace: '/var/jenkins_home/jobs/SolidBlue3_Metrics/workspace')
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 (4 found, 0 not found)
Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)
-> resolved module names for 15 issues
Resolving package names (or namespaces) by parsing the affected files
-> resolved package names of 4 affected files
No filter has been set, publishing all 15 issues
Creating fingerprints for all affected code blocks to track issues over different builds
-> created fingerprints for 15 issues (skipped 0 issues)
Copying affected files to Jenkins' build folder '/var/jenkins_home/jobs/SolidBlue3_Metrics/builds/28/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
Obtaining reference build from same job (SolidBlue3 :: Metrics)
Using reference build 'SolidBlue3_Metrics #27' to compute new, fixed, and outstanding issues
Issues delta (vs. reference build): outstanding: 15, new: 0, fixed: 0
No quality gates have been set - skipping
Health report is disabled - skipping
Created analysis result for 15 issues (found 0 new issues, fixed 0 issues)
Attaching ResultAction with ID 'javadoc-warnings' to build 'SolidBlue3_Metrics #28'.