JENA-2232: Fix javadoc production for java11#1144
Conversation
| is string based of WKT. | ||
| --> | ||
| <profile> | ||
| <id>java-after-8</id> |
There was a problem hiding this comment.
No-op. Jena now requires java11.
| <artifactId>maven-javadoc-plugin</artifactId> | ||
| <configuration> | ||
| <!-- Java 11 only, removed at Java13 --> | ||
| <additionalOptions>--no-module-directories</additionalOptions> |
There was a problem hiding this comment.
Does it break the build if someone uses Java13?
There was a problem hiding this comment.
Java 13 is EOL. The non-LTS have a lifetime of 6 months. No one should be using it (but ...)
It is not a problem in Java17 (which is LTS).
What does matter is that the flag has been removed and is illegal from Java13 and importantly in Java17 (the javadoc plugin exits with an error).
https://bugs.openjdk.java.net/browse/JDK-8215291 says fixed at 13 (and the flag --no-module-directories removed).
The fix has been backported to java 12.
There is an open task to backport to Java11 (LTS) but no progress.
https://bugs.openjdk.java.net/browse/JDK-8244171
There was a problem hiding this comment.
It is not a problem in Java17 (which is LTS).
Ah, perfect. I thought it would break on 13+, not only on 13 👍
Thanks! #TodayILearned :)
2 participants
No description provided.