In JDK1.5, the way one specifies that an entity has been deprecated has been
formally described as part of the Java Language Specification, and the behavior
of compilers is now guaranteed by virtue of its inclusion there. Deprecation
is specified by using the new java.lang.Deprecation marker annotation. While
javac will continue to respect the javadoc tag for some time, that is not a
guaranteed part of the platform specification. Other compilers, and future
javac compilers, cannot be guaranteed to respect the nonnormative javadoc tags.

A sweep should be made through the JDK source base adding @Deprecated to all
entities that are deprecated. The @deprecated javadoc tag should remain in
the documentation to describe the reasons and alternatives for the deprecated
API element (in the same way that @throws javadoc tag explains the reasons
for the "throws" of a method definition).