[
https://issues.apache.org/jira/browse/KAFKA-13895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536082#comment-17536082
]
Ismael Juma commented on KAFKA-13895:
-------------------------------------
I thought the release script requested Java 17 for this precise reason:
https://github.com/apache/kafka/blob/1c28928b9502bd1bc28b4b1dc058fa033d75b558/release.py#L435
> Fix javadocs build with JDK < 12
> --------------------------------
>
> Key: KAFKA-13895
> URL: https://issues.apache.org/jira/browse/KAFKA-13895
> Project: Kafka
> Issue Type: Task
> Components: docs
> Reporter: Tom Bentley
> Priority: Minor
>
> While doing the "Website update process" in the 3.1.1 release I found that
> I'd broken the javadoc search functionality due to having build the Java docs
> with Java 11. Java < 12 [a
> bug|https://bugs.openjdk.java.net/browse/JDK-8215291] that means the javadoc
> search functionality adds /undefined/ in the URL path (even though links
> between pages otherwise work.
> We could fix the build.gradle to use {{-no-module-directories}} when running
> with javadoc < v12, but that will then break the links to the JDK classes
> javadocs from the Kafka javadoc, [as described
> here|https://github.com/spring-projects/spring-security/issues/10944].
> Alternatively we could change the release process docs to require building
> with Java 17. While this would fix the problem for the Javadocs published on
> the website, anyone building the javadocs for themselves would still be
> affected.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
