Bug 18531 - Should not warn about overriding deprecated abstract methods
Summary: Should not warn about overriding deprecated abstract methods
Status: RESOLVED DUPLICATE of bug 48335
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: 3.0 M6   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-31 17:43 EDT by Peter Burka CLA
Modified: 2003-12-14 15:09 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Burka CLA 2002-05-31 17:43:14 EDT
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).
Comment 1 Jerome Lanneluc CLA 2002-05-31 18:01:02 EDT
Note the warning will disappear if you mark the overriding method as deprecated.
Comment 2 Philipe Mulet CLA 2002-06-01 04:16:40 EDT
We match javac behavior. May reconsider post 2.0
Comment 3 Philipe Mulet CLA 2003-10-30 04:51:13 EST
Current behavior will remain.
Comment 4 Philipe Mulet CLA 2003-12-14 15:08:50 EST
Reopen
Comment 5 Philipe Mulet CLA 2003-12-14 15:09:09 EST

*** This bug has been marked as a duplicate of 48335 ***