JDK 11+ and Javadoc

java maven javadoc java-11 maven-javadoc-plugin
Rafael Ibasco picture Rafael Ibasco · Nov 13, 2019 · Viewed 7.4k times · Source 
Exit code: 1 - javadoc: error - The code being documented uses packages in the unnamed module, but the packages defined in https://docs.oracle.com/en/java/javase/11/docs/api/ are in named modules.

Has anyone been able to make javadoc work without having to change the source version to 1.8 (as suggested in other forums)? I'm using JDK v11.0.5 and the issue still present (also with JDK 12+).

Edit: This error originated from maven and thrown by the maven-javadoc-plugin. I have not been able to make it work for JDK 11+ even with the <source>8</source> configuration.

Answer

Roman Grigoriadi picture Roman Grigoriadi · Feb 20, 2020

As suggested in OpenJDK issue tracker this can be worked around with defining source on Javadoc plugin:

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-javadoc-plugin</artifactId>
    <configuration>
        <source>8</source>
    </configuration>
</plugin>

Related questions

Maven is not working in Java 8 when Javadoc tags are incomplete

Since I use Maven I have been able to build and install in my local repository projects that have incomplete Javadoc tags (for example, a missing parameter). However, since I migrated to Java 8 (1.8.0-ea-b90) Maven is absolutely strict about missing …

Read More
Javadoc in JDK 8 : Invalid "self-closing element not allowed"

What are the best workarounds when running javadoc using JDK 8 and one receives this error. It seems that for JDK 8 it has been decided that tags like <br /> and <p /> should generate errors, because they are …

Read More
Maven checkstyle error : Expected @param tag for '<T>'

I have following method with generic types, but when I run maven checkstyle(maven-checkstyle-plugin, 2.121) it kept gives me Expected @param tag for '<T>' error message during maven build. How do I get over with this? /** * Read …

Read More