[
https://issues.apache.org/jira/browse/MJAVADOC-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17900688#comment-17900688
]
Elliotte Rusty Harold commented on MJAVADOC-732:
------------------------------------------------
If we're going to 9, I'd go to 11. 9 and 10 aren't worth considering. But my
inclination is to stick with 8 for a while longer. This should be available in
java 8. See
https://docs.oracle.com/javase/8/docs/technotes/guides/javadoc/whatsnew-8.html
> Use javax.tools API for calling javadoc
> ---------------------------------------
>
> Key: MJAVADOC-732
> URL: https://issues.apache.org/jira/browse/MJAVADOC-732
> Project: Maven Javadoc Plugin
> Issue Type: Improvement
> Components: javadoc
> Reporter: Konrad Windszus
> Priority: Major
>
> Currently javadoc is called as external process which makes
> consuming/exposing warnings and errors a bit cumbersome and also prevents
> proper m2e integration.
> As https://openjdk.org/jeps/106 added javadoc support to {{javax.tools}} with
> Java 8 it should be safe to adopt that given that m-javadoc-p has been
> updated to require Java 8 in MJAVADOC-675
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
