P3
javac still detects and treats specially the character string `@deprecated` in a documentation comment: in particular, it sets the DEPRECATED flag for the declaration.
This is archaic behavior from before annotations (and `@Deprecated`) were added in JDK 1.5.
For a long time now, standard practice has been to use the `@Deprecated` annotation to indicate deprecation, with the `@deprecated` tag used to provide descriptive information about why the declaration is deprecated.
The detection of the `@deprecated` string effectively became broken when we changed the doc comment parser to ignore potential block tags (like `@deprecated`) when they appear in an inline tag.
It is time to remove this legacy treatment of the "@deprecated" string in a doc comment ... i.e. detecting the string and marking the declaration as DEPRECATED even if the @Deprecated annotation is not present.
Separately, we already give a warning if the tag is found but the annotation is not found.The implementation of that warning may need to change and become a doclint or javadoc-only warning.
This is archaic behavior from before annotations (and `@Deprecated`) were added in JDK 1.5.
For a long time now, standard practice has been to use the `@Deprecated` annotation to indicate deprecation, with the `@deprecated` tag used to provide descriptive information about why the declaration is deprecated.
The detection of the `@deprecated` string effectively became broken when we changed the doc comment parser to ignore potential block tags (like `@deprecated`) when they appear in an inline tag.
It is time to remove this legacy treatment of the "@deprecated" string in a doc comment ... i.e. detecting the string and marking the declaration as DEPRECATED even if the @Deprecated annotation is not present.
Separately, we already give a warning if the tag is found but the annotation is not found.The implementation of that warning may need to change and become a doclint or javadoc-only warning.