commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vamsi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COLLECTIONS-653) Update Javadoc to Build on Java 1.8
Date Mon, 11 Sep 2017 05:05:00 GMT

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

Vamsi commented on COLLECTIONS-653:
-----------------------------------

[~chtompki] I was looking into this issue. There are plenty of issues in the java doc because
of the new content check introduced in Java 8 [http://docs.oracle.com/javase/8/docs/technotes/guides/javadoc/whatsnew-8.html].
I am thinking of resolving this in two steps.

1) Disable doclint by introducing a new profile in POM only for Java 8 and above ( until all
the issues are fixed )
2) Fix all the issues in java doc and enable doclint

Hope it makes sense. Please let me know your thoughts.

> Update Javadoc to Build on Java 1.8
> -----------------------------------
>
>                 Key: COLLECTIONS-653
>                 URL: https://issues.apache.org/jira/browse/COLLECTIONS-653
>             Project: Commons Collections
>          Issue Type: Improvement
>    Affects Versions: 4.1
>            Reporter: Rob Tompkins
>
> Currently {{mvn clean site}} only works when building with Java 7, we need to update
the javadoc to accommodate the requisite changes for building on Java 8 as the code does compile
on Java 8.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message