[ 
https://issues.apache.org/jira/browse/APEXCORE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477475#comment-16477475
 ] 

ASF GitHub Bot commented on APEXCORE-569:
-----------------------------------------

tweise closed pull request #600: APEXCORE-569 : Fixing javadoc errors with jdk8
URL: https://github.com/apache/apex-core/pull/600
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/pom.xml b/pom.xml
index ac12195e2f..3482d473f0 100644
--- a/pom.xml
+++ b/pom.xml
@@ -332,6 +332,9 @@
           <groupId>org.apache.maven.plugins</groupId>
           <artifactId>maven-javadoc-plugin</artifactId>
           <version>2.9</version>
+          <configuration>
+            <additionalparam>-Xdoclint:none</additionalparam>
+          </configuration>
         </plugin>
         <plugin>
           <groupId>org.codehaus.mojo</groupId>


 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Fix javadoc errors uncovered by Java 8
> --------------------------------------
>
>                 Key: APEXCORE-569
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-569
>             Project: Apache Apex Core
>          Issue Type: Improvement
>            Reporter: Munagala V. Ramanath
>            Assignee: Munagala V. Ramanath
>            Priority: Major
>
> Running "mvn javadoc:aggregate" with Java 8 produces numerous errors 
> resulting from stricter checking; see for example 
> http://blog.joda.org/2014/02/turning-off-doclint-in-jdk-8-javadoc.html
> We should fix these errors.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to