Bug 20769 - Superfluous warning: implementing deprecated abstract method
Summary: Superfluous warning: implementing deprecated abstract method
Status: RESOLVED DUPLICATE of bug 48335
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC other
: P3 normal (vote)
Target Milestone: 3.0 M6   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-06-20 22:13 EDT by Eric Nickell CLA
Modified: 2003-12-14 15:07 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Nickell CLA 2002-06-20 22:13:44 EDT 
Some of us like to keep our warnings set tight, and keep our warnings count at
zero.  For us, it's frustrating to have a warning that you have to live with.  I
feel it trains people to ignore warnings.

When MyClass implements a deprecated method in an interface, this should not
generate a warning.  *Calling* a deprecated method should generate a warning. 
But MyClass *has* to implement it.

Somewhat more debatable: Implementing or overriding a deprecated method, imho,
should also not generate warnings.  Again, it is the calling of the method which
is deprecated, because the API implementors are claiming there is another way to
get the same functionality.
Comment 1 Jerome Lanneluc CLA 2002-06-21 05:34:44 EDT 
Please make sure that the method that implements the deprecated interface 
method is tagged with "@deprecated" as well. The warning will then disappear.
Comment 2 Philipe Mulet CLA 2002-06-21 06:44:16 EDT 
Our behavior is identical to javac. 
Not critical, might reconsider post 2.0
Comment 3 Eric Nickell CLA 2002-06-21 11:07:06 EDT 
Since javac is not and does not have an integrated editor, I fail to see how
eclipse's behavior (in this area) is identical to javac's.  As I mentioned, the
compiler (like javac's) is happy with this arrangement, but the editor continues
to suggest a course of action, which if followed, is impotent.

I agree that it should be pushed past 2.0, BUT the aberrant behavior should be
documented in the readme.
Comment 4 Eric Nickell CLA 2002-06-21 11:08:19 EDT 
Please ignore previous comment.  It was missent to the wrong bug report.
Comment 5 Eric Nickell CLA 2002-06-21 12:11:33 EDT 
(Paying careful attention this time to *which* bug I'm making comments on...)

Here is an alternative that would be just as useful to me:

In the Windows/Preferences/Java/Compiler/Errors and Warnings tab, split "Usage
of deprecated API" into two separate issues, "Accessing deprecated
members/classes" and "Overriding/implementing deprecated methods".
Comment 6 Philipe Mulet CLA 2003-12-14 15:07:29 EST 
Reopen
Comment 7 Philipe Mulet CLA 2003-12-14 15:07:59 EST 

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