JDK-8068626 : Add javac lint warning when the @Deprecated annotation is used where it is a no-op
- Type: Enhancement
- Component: tools
- Sub-Component: javac
- Affected Version: 9
- Priority: P4
- Status: Closed
- Resolution: Fixed
- Submitted: 2015-01-07
- Updated: 2016-08-19
- Resolved: 2016-08-12
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 b132Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
While the @Deprecated annotation can be applied most everywhere, there are several uses of it that are specified as being no-ops (JDK-6481080): * parameters * local variables * package declarations It could be helpful if javac's -Xlint:deprecation warning including a warning for no-op uses of @Deprecated.
Comments
|