[
https://issues.apache.org/jira/browse/IGNITE-13202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17856749#comment-17856749
]
Ignite TC Bot commented on IGNITE-13202:
----------------------------------------
{panel:title=Branch: [pull/11403/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/11403/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7922731&buildTypeId=IgniteTests24Java8_RunAll]
> 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
> Assignee: Maksim Timonin
> Priority: Major
> Labels: ise
>
> 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 generation command: {{mvn initialize -Pjavadoc}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
