Bugzilla – Full Text Bug Listing
| Summary: | Should not warn about overriding deprecated abstract methods | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Peter Burka <peter_burka> |
| Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | minor | ||
| Priority: | P3 | ||
| Version: | 2.0 | ||
| Target Milestone: | 3.0 M6 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
Note the warning will disappear if you mark the overriding method as deprecated. We match javac behavior. May reconsider post 2.0 Current behavior will remain. Reopen |
Build F1 Consider an interface interface I { /** * @deprecated */ public void foo(); } If I implement this interface in public class Foo implements I { public void foo() {} } I get a warning that Foo overrides deprecated method foo() from I. This warning should not be reported, since I have no choice but to implement the method! If I did not, I would get an error. I believe that it's reasonable to warn about implementing a deprecated interface, or for overriding a non-abstract deprecated method, but not for overriding a deprecated abstract method. (javac seems to have the same behaviour as Eclipse, at least if the classes are in separate files).