You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2020/07/02 08:16:00 UTC
[jira] [Updated] (IGNITE-13202) Javadoc HTML can't be generated
correctly with maven-javadoc-plugin on JDK 11+
[ https://issues.apache.org/jira/browse/IGNITE-13202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Plekhanov updated IGNITE-13202:
---------------------------------------
Description:
Javadoc utility has some bugs which don't allow to build Ignite Javadocs correctly ({{mvn initialize -Pjavadoc}}).
Building javadoc under JDK 11+ throws an error "The code being documented uses modules but the packages defined in
[https://docs.oracle.com/javase/8/docs/api] are in the unnamed module". To workaround this error argument "source=1.8" can be specified, but there is another bug related to "source" and "subpackages" argument usages: [https://bugs.openjdk.java.net/browse/JDK-8193030.] We still can build javadoc with disabled {{detectJavaApiLink}} maven-javadoc-plugin option, but in this case there will be no references to Java API from Ignite Javadoc.
Also, there is a bug with "-exclude" argument in JDK 11+, it doesn't exclude subpackages of specified to exclude packages, so in generated output there is a lot of javadocs for internal packages.
was:
Javadoc utility has some bugs which don't allow to build Ignite Javadocs correctly.
Building javadoc under JDK 11+ throws an error "The code being documented uses modules but the packages defined in
https://docs.oracle.com/javase/8/docs/api are in the unnamed module". To workaround this error argument "source=1.8" can be specified, but there is another bug related to "source" and "subpackages" argument usages: [https://bugs.openjdk.java.net/browse/JDK-8193030.] We still can build javadoc with disabled {{detectJavaApiLink}} maven-javadoc-plugin option, but in this case there will be no references to Java API from Ignite Javadoc.
Also, there is a bug with "-exclude" argument in JDK 11+, it doesn't exclude subpackages of specified to exclude packages, so in generated output there is a lot of javadocs for internal packages.
> Javadoc HTML can't be generated correctly with maven-javadoc-plugin on JDK 11+
> ------------------------------------------------------------------------------
>
> Key: IGNITE-13202
> URL: https://issues.apache.org/jira/browse/IGNITE-13202
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksey Plekhanov
> Priority: Major
>
> Javadoc utility has some bugs which don't allow to build Ignite Javadocs correctly ({{mvn initialize -Pjavadoc}}).
> Building javadoc under JDK 11+ throws an error "The code being documented uses modules but the packages defined in
> [https://docs.oracle.com/javase/8/docs/api] are in the unnamed module". To workaround this error argument "source=1.8" can be specified, but there is another bug related to "source" and "subpackages" argument usages: [https://bugs.openjdk.java.net/browse/JDK-8193030.] We still can build javadoc with disabled {{detectJavaApiLink}} maven-javadoc-plugin option, but in this case there will be no references to Java API from Ignite Javadoc.
> Also, there is a bug with "-exclude" argument in JDK 11+, it doesn't exclude subpackages of specified to exclude packages, so in generated output there is a lot of javadocs for internal packages.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)