JDK-8215580 : Remove support for `--no-module-directories`
- Type: Sub-task
- Component: tools
- Sub-Component: javadoc(tool)
- Affected Version: 13
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2018-12-18
- Updated: 2019-05-21
- Resolved: 2019-04-23
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 13 |
|---|
13 b18Fixed  |
Related Reports
|
Blocks :
|
|
|
Blocks :
|
|
|
CSR :
|
|
|
Relates :
|
Description
When modules were added to Java 9, javadoc did not initially take them into account in the structure of the generated output hierarchy, meaning that like-named packages in different modules could overlap. This was remedied in ... (JDK-8195795) but for temporary backward compatibility, an option was added to revert to the earlier, bad behavior. It is now time to remove support for the old behavior, and to remove the option that enables it.
Comments
|