-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
P3
-
Affects Version/s: 11.0.2
-
Component/s: tools
-
Environment:
openjdk version "11.0.2" 2019-01-15
OpenJDK Runtime Environment 18.9 (build 11.0.2+9)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.2+9, mixed mode)OS Name: Microsoft Windows 10 Pro
OS Version: 10.0.17134 N/A Build 17134
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Freeopenjdk version "11.0.2" 2019-01-15 OpenJDK Runtime Environment 18.9 (build 11.0.2+9) OpenJDK 64-Bit Server VM 18.9 (build 11.0.2+9, mixed mode) OS Name: Microsoft Windows 10 Pro OS Version: 10.0.17134 N/A Build 17134 OS Manufacturer: Microsoft Corporation OS Configuration: Standalone Workstation OS Build Type: Multiprocessor Free
When creating a Multi-Release jar, it is allowed to have a module descriptor in the versioned-folder and not in the root of the jar.
e.g.
some/Util.class
META-INF/versions/11/module-info.class
META-INF/versions/11/some/Util.class
When trying to generate javadoc for such jar, it'll exit with the message: error: module not found: <some.modulename>
Moving the module descriptor to the root will make it succeed.
e.g.
some/Util.class
META-INF/versions/11/module-info.class
META-INF/versions/11/some/Util.class
When trying to generate javadoc for such jar, it'll exit with the message: error: module not found: <some.modulename>
Moving the module descriptor to the root will make it succeed.
- duplicates
-
JDK-8234766 Javadoc does not support module-info in a multi-release jar
-
- Resolved
-
- relates to
-
-
- Closed
-
-
-
- Resolved
-
- links to