[
https://issues.apache.org/jira/browse/CALCITE-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110885#comment-17110885
]
Carlos Saltos commented on CALCITE-2836:
----------------------------------------
Adding {{<detectJavaApiLink>false</detectJavaApiLink>}} to the Maven javadoc
pluging configuration also fix the error as a workaround
> Remove maven-compiler-plugin from calcite-plus module pom.xml
> -------------------------------------------------------------
>
> Key: CALCITE-2836
> URL: https://issues.apache.org/jira/browse/CALCITE-2836
> Project: Calcite
> Issue Type: Bug
> Components: build
> Reporter: Kevin Risden
> Assignee: Kevin Risden
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.19.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> It looks like JDK 11.0.2+ has an issue where 1.8 being specified causes
> javadoc to fail. This has failed for the last few builds on Travis with the
> following error message in the calcite-plus module:
> {code:java}
> javadoc: 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.
> {code}
> There is a related JDK bugs about this:
> * [https://bugs.openjdk.java.net/browse/JDK-8212233]
> There is a listed work around but I tested and if we cleanup the leftover
> maven-compiler-plugin part from calcite-plus module this issue goes away.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
