AspectJ - Messages

Successfully parsed console log
-> found 13 issues (skipped 27 duplicates)
Parsing console log (workspace: '/var/jenkins_home/jobs/blueHour_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/blueHour_Metrics/workspace'
-> none of the issues requires resolving of paths
Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)
-> resolved module names for 13 issues
Resolving package names (or namespaces) by parsing the affected files
-> resolved package names of 1 affected files
No filter has been set, publishing all 13 issues
Creating fingerprints for all affected code blocks to track issues over different builds
-> created fingerprints for 0 issues (skipped 13 issues)
Copying affected files to Jenkins' build folder '/var/jenkins_home/jobs/blueHour_Metrics/builds/1318/files-with-issues'
-> 0 copied, 0 not in workspace, 13 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 13 issues (found 0 new issues, fixed 0 issues)
Attaching ResultAction with ID 'aspectj' to build 'blueHour_Metrics #1318'.