JDK-6591404 : Need to investigate and cleanup javadoc code for using internal javac classes
- Type: Enhancement
- Component: tools
- Sub-Component: javadoc(tool)
- Affected Version: 7
- Priority: P4
- Status: Closed
- Resolution: Duplicate
- OS: windows_xp
- CPU: x86
- Submitted: 2007-08-09
- Updated: 2011-01-25
- Resolved: 2011-01-25
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 7 |
|---|
7Resolved  |
Related Reports
|
Duplicate :
|
Description
Introducing a new FileObject implementation would break the javadoc tool. File JavadocClassReader.java reffers to ZipFileObject (does an instanceof test.) Whenever a new FileObject is added the JavaDoc tool doesn't know how to deal with it.
Comments
|