You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2023/11/28 12:50:00 UTC

[jira] [Commented] (MJAVADOC-732) Use javax.tools API for calling javadoc

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

Elliotte Rusty Harold commented on MJAVADOC-732:
------------------------------------------------

see https://stackoverflow.com/questions/54040274/what-is-the-alternative-of-com-sun-tools-javadoc-main-execute-to-run-doclet-in-j

> 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)