JDK-8000741 : refactor javadoc to use abstraction to handle relative paths
- Type: Bug
- Component: tools
- Sub-Component: javadoc(tool)
- Priority: P4
- Status: Resolved
- Resolution: Duplicate
- Submitted: 2012-10-10
- Updated: 2012-11-09
- Resolved: 2012-10-18
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 8 |
|---|
8 b64Resolved  |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
Description
javadoc currently passes around one or more strings to represent a path, and possible the inverse of the path. The strings are supposed to obey an invariant that they end in '/' which complicates the code and causes issues when the invariant is not valid. It would be better to introduce a new abstraction to represent such paths.