Re: Maven issue with JDK16 - javac and javadoc

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: Maven issue with JDK16 - javac and javadoc

Romain Manni-Bucau
+1, got some weirdness on j11 too. We should really have a way to ignore
these errors, it is too impacting, in particular when javadoc are only
deployed to make central or our nexus happy.

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>


Le jeu. 12 nov. 2020 à 13:03, Enrico Olivelli <[hidden email]> a
écrit :

> Hi folks,
> I have fallen into this issue about Maven + Maven Compiler Plugin + JDK16
>
> This is the issue on JDK issue tracking
> https://bugs.openjdk.java.net/browse/JDK-8253996
>
> Basically -Xdoclint:missing does not work anymore when you run javac inside
> the same JVM as Maven core, because the JVM lacks the jdk.javadoc module.
> If you run javac in "fork" mode the problem is not present because the
> external "javac" program loads correctly jdk.javadoc module and is able to
> execute "-Xdoclint"
>
> it looks like we have to fix it on Maven, I am not sure the problem is
> about maven-compiler-plugin or plexus compiler, as it is because the JVM
> that executes Maven core lacks the jdk.javadoc module.
>
> On the JDK side it looks like the issue is to be closed as "works for me"
>
>
> Thoughts?
> Enrico
>