JDK-8177371 : Release Note: Compiler will emit a warning if deprecated javadoc tag is used without @Deprecated annotation
- Type: Sub-task
- Component: tools
- Sub-Component: javac
- Affected Version: 9
- Priority: P4
- Status: Closed
- Resolution: Delivered
- Submitted: 2017-03-22
- Updated: 2017-09-22
- Resolved: 2017-04-07
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 |
|---|
9Resolved  |
Description
If the javadoc deprecated tag is used on an element without it also being deprecated using the @Deprecated annotation,
the compiler will by default produce a new warning to this effect.
The new warning can be suppressed either by adding the command line option -Xlint:-dep-ann to the javac command line or by using
@SuppressWarnings("dep-ann") annotation (as with any other warning-suppressing annotation, it is always a good practice to add
such an annotation as close to the member being deprecated as possible).
In a future version of Java SE, the compiler may no longer treat @deprecated javadoc tag as indicating formal deprecation.
Comments
|