Bug 198831

Summary:	Cause an error for use of specific deprecated APIs rather than an all-or-nothing warning/error choice
Product:	[Eclipse Project] JDT	Reporter:	Dave Boden <dave>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	3.3
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Dave Boden

2007-08-03 13:16:03 EDT

Build ID: M20070212-1330

Steps To Reproduce:
This is a new feature request.

Old API classes such as java.util.Date have deprecated methods that are "more deprecated" than others. These methods should have been removed years ago and are the source of serious bugs when they're used.

Use of a deprecated method in Log4J is nowhere near as serious, and I'm happy to tolerate it in my projects.

So, what I'm looking for is a feature that will allow me to flag java.util.Date or perhaps even specific methods in java.util.Date as super-deprecated. These should cause an error even if most of my deprecations only result in a warning.

More information: