[
https://issues.apache.org/jira/browse/MAHOUT-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16787107#comment-16787107
]
Andrew Palumbo commented on MAHOUT-2060:
----------------------------------------
this may help:
https://www.oracle.com/technetwork/java/javase/downloads/java-doc-updater-tool-1955731.html
>From The readme: Java API Documentation Updater Tool
To address CVE-2013-1571, users hosting publicly facing Java API Documentation
generated with javadoc 5u45, 6u45, 7u21 or earlier are strongly encouraged to
re-create the Java API documentation using javadoc from 7u25 or above.
{quote}
Alternatively, for convenience of users and for those who have further modified
the generated documentation, Oracle provides the Java API Documentation
Updater, a repair-in-place tool.
Source code is available with the download if you have a non-standard
environment. The Java API Documentation Updater Tool is a separate download and
not included in any JDK/JRE bundles. Please also see important information
related to the javadoc tool in the Known Issues section.
{quote}
> Fix Java Docs
> -------------
>
> Key: MAHOUT-2060
> URL: https://issues.apache.org/jira/browse/MAHOUT-2060
> Project: Mahout
> Issue Type: Improvement
> Affects Versions: 0.14.0, 0.14.1
> Reporter: Trevor Grant
> Priority: Minor
>
> When building Javadocs with Java8 errors are thrown and builds crash.
> The band aid was (in Jenkins) to add {{-Dmaven.javadoc.skip=true to nightly
> and quality builds. }}
>
> {{Better to fix the javadoc errors (which expose as warnings on mvn install).
> }}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
