JavaDoc - Messages
Information Messages
Successfully parsed console log-> found 16 issues (skipped 42 duplicates)Successfully parsed console log-> found 16 issues (skipped 42 duplicates)Successfully parsed console log-> found 16 issues (skipped 42 duplicates)Successfully parsed console log-> found 16 issues (skipped 42 duplicates)Parsing console log (workspace: '/home/jenkins/agent/workspace/eclipselink-build-verifier')Post processing issues on 'basic-wg42k' 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/eclipselink-build-verifier'-> resolved paths in source directory (6 found, 0 not found)Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)-> resolved module names for 16 issuesResolving package names (or namespaces) by parsing the affected files-> resolved package names of 6 affected filesNo filter has been set, publishing all 16 issuesCreating fingerprints for all affected code blocks to track issues over different builds-> created fingerprints for 16 issues (skipped 0 issues)Copying affected files to Jenkins' build folder '/var/jenkins/jobs/eclipselink-build-verifier/builds/49/files-with-issues'-> 3 copied, 0 not in workspace, 0 not-found, 0 with I/O errorRepository miner is not configured, skipping repository miningReference build recorder is not configuredObtaining reference build from same job (eclipselink-build-verifier)Using reference build 'eclipselink-build-verifier #48' to compute new, fixed, and outstanding issuesIssues delta (vs. reference build): outstanding: 16, new: 0, fixed: 0No quality gates have been set - skippingHealth report is disabled - skippingCreated analysis result for 16 issues (found 0 new issues, fixed 0 issues)Attaching ResultAction with ID 'javadoc-warnings' to build 'eclipselink-build-verifier #49'.