Bug 198831 - Cause an error for use of specific deprecated APIs rather than an all-or-nothing warning/error choice
Summary: Cause an error for use of specific deprecated APIs rather than an all-or-noth...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-03 13:16 EDT by Dave Boden CLA
Modified: 2007-08-08 08:37 EDT (History)
0 users

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 Dave Boden CLA 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: