Javadoc task fails (module not found)
See original GitHub issueThe dependencies are configured like this:
dependencies {
implementation(
[...]
'net.bytebuddy:byte-buddy:1.9.11',
[...]
)
[...]
}
The module-info.java looks like this:
open module [...] {
[...]
requires net.bytebuddy;
[...]
}
It results in an error when executing the javadoc task:
[...]\src\main\java\module-info.java:3: error: module not found: net.bytebuddy
requires net.bytebuddy;
ByteBuddy is a multi release jar with the module-info.class inside META-INF/versions/9
Seems to be related to this issue which is already closed: https://github.com/java9-modularity/gradle-modules-plugin/issues/13
Issue Analytics
- State:
- Created 4 years ago
- Comments:5
Top Results From Across the Web
Javadoc task fails: Cannot find module org.apache.logging.log4j
Running Gradle 4.8 with Java 10. Log4j 2 is a Java module, but it doesn't have the module-info.
Read more >"Module not found" message when generating JavaDocs in ...
The problem is that Eclipse does not automatically pass information related to the JavaFX module to the JavaDoc call.
Read more >Javadoc Task - Apache Ant
Specify where to find user class files by reference to a classpath defined elsewhere. No. bootclasspathref, Override location of class files loaded by...
Read more >Dokka javadoc task fails with JDK 11 reporting missing ...
Executing Dokka javadoc task with JDK 11 fails. Tested with Maven-based project with Dokka configured, I can provide details if necessary. NB: No...
Read more >How to force javadoc generation in presence of errors? - Eclipse
There is no "cannot find module" error. However, although this creates the doc folder, that folder is empty, it still does not generate...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Closing because of inactivity. Issue doesn’t seem to be related with the plugin.
I came across this issue and started a quick search.
It is known with the JDK people and has been fixed: JDK-8208269.
Supposedly the fix was backported to JDK version
11.0.5
as well (long-time support)