JDK-8014634 : JSR 292 javadoc needs cleanups and clarifications
- Type: Bug
- Component: core-libs
- Sub-Component: java.lang.invoke
- Affected Version: 8
- Priority: P4
- Status: Closed
- Resolution: Duplicate
- Submitted: 2013-05-15
- Updated: 2013-10-01
- Resolved: 2013-10-01
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 |
|---|
8Resolved  |
Related Reports
|
Duplicate :
|
Description
The javadoc tool running on the source files for java.lang.invoke turns up a lot of errors and warnings. Some of the errors cause the tool to bail out in some build modes. Some of the source code examples have naked '<' and '>' characters which need to be replaced by html entities. Some of the language is imprecise, such as a sentence in Lookup which seems to refer to the return value of a constructor. Fixing or clarifying these issues does not change types or behavior of the API, with the following minor exceptions: - (none at present)