JDK-8215582 : Remove support for `--no-module-directories`
  • Type: CSR
  • Component: tools
  • Sub-Component: javadoc(tool)
  • Priority: P3
  • Status: Closed
  • Resolution: Approved
  • Fix Versions: 13
  • Submitted: 2018-12-18
  • Updated: 2019-04-18
  • Resolved: 2019-04-18
Related Reports
CSR :  
JDK-8215580 - Remove support for `--no-module-directories`
Description
Summary
-------

Remove support for the organizational hierarchy for module-oriented documentation as used in JDK 9 and JDK 10.


Problem
-------

When javadoc added support for modules in JDK 9, it did not initially include an extra level of directory in the output hierarchy. That was addressed in JDK 11, along with an option to revert to the old layout in case of need.  Maintaining support for the old layout is a maintenance burden and there is no use-case for supporting the old inferior layout.

Solution
--------

Remove support for the old package-oriented hierarchy, and for the `--no-module-directories` option that enables it.

Specification
-------------

The `--no-module-directories` option is removed.

The generated file hierarchy will always include a directory level for the module name.
Comments
There is no change in behavior when the code being processed does not contain modules. This includes all code for --release before 9, and for package-oriented code for later releases ... i.e. using --source-path with no module-info.java. For the record, there was never a check that the option was being used redundantly ... i.e. specified `--no-module-directories` for package oriented code.
18-04-2019
Moving to Approved. I assume there is no change in output for --release values before 9.
18-04-2019