JDK-8141359 : @Deprecated on packages should be clarified
- Type: Sub-task
- Component: core-libs
- Sub-Component: java.lang
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2015-11-03
- Updated: 2015-11-20
- Resolved: 2015-11-04
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 9 |
|---|
9 b92Fixed  |
Description
The fix for JDK-6481080 adds wording to the effect that the @Deprecated annotation on a variety of program elements "has no effect." The intent here is that @Deprecated in these locations does not have the effect of causing the compiler to emit warnings. This should be clarified. For packages, at least, @Deprecated on a package will cause the annotation to be compiled into the class and be made available at runtime, since @Deprecated has runtime retention. It may indeed be that @Deprected on a local variable or method parameter has no effect whatsoever. It might be worth clarifying that, too.
Comments
|