JDK-8226254 : Javadoc tool doesn't respect module descriptor in Multi-Release folder
- Type: Bug
- Component: tools
- Sub-Component: javadoc(tool)
- Affected Version: 11.0.2
- Priority: P3
- Status: Resolved
- Resolution: Duplicate
- Submitted: 2019-06-17
- Updated: 2020-06-15
- Resolved: 2020-06-15
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 15 |
|---|
15Resolved  |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
|
|
Relates :
|
Description
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.
Comments
|