The annotation type java.lang.Deprecated does not have an explicit @Target meta-annotation; therefore, in can be applied in all possible locations even though it is not meaningful in some of those locations. As part of JSR 308, new locations were added and thereby Deprecated can now appear in still more locations without defined meaning.
See also discussion in thread
http://mail.openjdk.java.net/pipermail/core-libs-dev/2010-January/thread.html#3489
See
http://hg.openjdk.java.net/jdk7/tl/jdk/rev/fa0cb25202d8
See also discussion in thread
http://mail.openjdk.java.net/pipermail/core-libs-dev/2010-January/thread.html#3489
See
http://hg.openjdk.java.net/jdk7/tl/jdk/rev/fa0cb25202d8
- relates to
-
JDK-7015156 Remove JSR 308 changes from core libraries
-
- Closed
-
-
JDK-8068626 Add javac lint warning when the @Deprecated annotation is used where it is a no-op
-
- Closed
-
-
-
- Closed
-