JavaDoc - Messages
Information Messages
Successfully parsed console log-> found 30 issues (skipped 0 duplicates)Successfully parsed console log-> found 30 issues (skipped 0 duplicates)Successfully parsed console log-> found 30 issues (skipped 0 duplicates)Successfully parsed console log-> found 30 issues (skipped 0 duplicates)Parsing console log (workspace: '/home/jenkins/agent/workspace/jws-api-master-build')Post processing issues on 'basic-72m33' 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 source directory '/home/jenkins/agent/workspace/jws-api-master-build'-> resolved paths in source directory (8 found, 0 not found)Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)-> resolved module names for 30 issuesResolving package names (or namespaces) by parsing the affected files-> resolved package names of 8 affected filesNo filter has been set, publishing all 30 issuesCreating fingerprints for all affected code blocks to track issues over different builds-> created fingerprints for 30 issues (skipped 0 issues)Copying affected files to Jenkins' build folder '/var/jenkins/jobs/jws-api-master-build/builds/36/files-with-issues'-> 8 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 (JWS API master build)Using reference build 'jws-api-master-build #35' to compute new, fixed, and outstanding issuesIssues delta (vs. reference build): outstanding: 30, new: 0, fixed: 0No quality gates have been set - skippingHealth report is disabled - skippingCreated analysis result for 30 issues (found 0 new issues, fixed 0 issues)Attaching ResultAction with ID 'javadoc-warnings' to build 'jws-api-master-build #36'.