JDK-8251921 : Expand default constructor warning to cover more cases
- Type: Enhancement
- Component: tools
- Sub-Component: javac
- Affected Version: 16
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-08-18
- Updated: 2024-11-20
- Resolved: 2020-08-27
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 16 |
|---|
16 b14Fixed  |
Related Reports
|
CSR :
|
|
|
Relates :
|
|
|
Relates :
|
Description
As reported in off-list discussions with [~prr], there are situations where a protected class's default constructor can be exposed in an formal API. These situations are not covered by the warning implemented by JDK-8071961, but perhaps the warning should be extended to cover more cases.
Comments
|