Bug 122540 - Need a causedByClass field in Problems view (specially for deprecations)
Summary: Need a causedByClass field in Problems view (specially for deprecations)
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   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: 2006-01-03 13:19 EST by Peter Larsen CLA
Modified: 2006-01-04 10:48 EST (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 Peter Larsen CLA 2006-01-03 13:19:50 EST 
There are a lot of warnings/errors that are cause by having discrepancy between 2 places. Currently the Problems view only shows 1 place.

E.g. Depricated code only shows where a deprivated function/class is used, not where it is depricated. Using a missing function (or wrong parameters) does not show in which class it is missing.

(Other warnings are only cause by one class. e.g. "the import ... is never used".)

The request is to have a causedby field in the problems view, so
we can sort/filter after that. Usually it is relevant when we
deprecated a class, and some are slow at converting their packages.
(Deprecating a class shows both as constructor X is deprecated and
function Y in X is deprecated, which makes it more annoying).
Comment 1 Martin Aeschlimann CLA 2006-01-04 10:48:48 EST 
The only thing we can do is to improve the error message. Additional columns are not possible. But I think the error message if good enough.