Bug 34850

Summary:	Need better control over deprecation messages
Product:	[Eclipse Project] JDT	Reporter:	Lance Eason <lance.eason>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	2.1
Target Milestone:	2.1 RC3
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description Lance Eason

2003-03-12 13:55:21 EST

I currently get two types of deprecation warnings. The first types of warnings 
is when I use a deprecated API, these are legitimate problems that I want to 
see in my task list and address.  The second type of deprecation warning is 
when one of my classes implements a deprecated method.  The reason my class is 
implementing a deprecated method though is that it is implementing an interface 
that has a deprecated method on it.  Not much I can do about that, the 
interface declares it so the class has to implement it deprecated or not.  I'd 
really rather not even see messages for that or at least be able to turn them 
off separately from the deprecation warnings I do care about.

Comment 1 Olivier Thomann

2003-03-12 16:17:57 EST

This is not a bug. It is a feature request.

Comment 2 Lance Eason

2003-03-12 16:26:18 EST

Yeah sorry about that meant to enter it as an enhancement.

Comment 3 Jerome Lanneluc

2003-03-13 05:39:25 EST

Just add /** @deprecated */ on the javadoc of the method that implements the 
deprecated interface, and the warning should go away.

Comment 4 Philipe Mulet

2003-03-13 12:04:58 EST

Note that by default we will not report deprecation inside deprecated code (you 
can re-enable this by changing the corresponding Java compiler preference).

Is it ok to close?

Comment 5 Philipe Mulet

2003-03-17 17:18:42 EST

Closing