JDK-8220382 : Cleanup doclet instantiation
- Type: Enhancement
- Component: tools
- Sub-Component: javadoc(tool)
- Affected Version: 13
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2019-03-08
- Updated: 2019-04-24
- Resolved: 2019-04-17
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 b17Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
Even after removing support for the old Doclet API (JDK-8215584, JDK-8219575, JDK-8219632) there are still echoes of the old world. See https://mail.openjdk.java.net/pipermail/javadoc-dev/2019-March/000937.html In particular, * there is almost-duplicated code to load a nominated class in Start.java, lines between 750-759 and 771-781 * the code to load the class is in Start.preprocess, but the code to create an instance is in Start.begin. It would be better to move the instantiate code into preprocess, so that it returns a Doclet, not a Class<?>