JDK-8199398 : Release Note: Missing Types Are Consistently Modeled as ERROR Types
- Type: Sub-task
- Component: tools
- Sub-Component: javac
- Affected Version: 11
- Priority: P4
- Status: Closed
- Resolution: Delivered
- Submitted: 2018-03-09
- Updated: 2019-04-09
- Resolved: 2018-05-10
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 11 |
|---|
11Resolved  |
Description
Missing types are now consistently modeled as ERROR types, and the `javac` internal exception, `CompletionFailure`, is no longer thrown to API clients. Previously, annotation processors and other `javax.lang.model` clients could, in some cases, observe missing types modeled as DECLARED types with a `javac` internal exception, `CompletionFailure`, thrown out of the model methods when manipulating such types.