Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8143521 | emb-9 | Joe Darcy | P4 | Resolved | Fixed | team |
The fix for JDK-6481080 adds wording to the effect that the @Deprecated annotation on a variety of program elements "has no effect." The intent here is that @Deprecated in these locations does not have the effect of causing the compiler to emit warnings.
This should be clarified. For packages, at least, @Deprecated on a package will cause the annotation to be compiled into the class and be made available at runtime, since @Deprecated has runtime retention.
It may indeed be that @Deprected on a local variable or method parameter has no effect whatsoever. It might be worth clarifying that, too.
This should be clarified. For packages, at least, @Deprecated on a package will cause the annotation to be compiled into the class and be made available at runtime, since @Deprecated has runtime retention.
It may indeed be that @Deprected on a local variable or method parameter has no effect whatsoever. It might be worth clarifying that, too.
- backported by
-
JDK-8143521 @Deprecated on packages should be clarified
-
- Resolved
-