Bug 485338 - Option to ignore dependent errors
Summary: Option to ignore dependent errors
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.5.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-07 07:27 EST by Marvin Fröhlich CLA
Modified: 2023-03-08 18:11 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 Marvin Fröhlich CLA 2016-01-07 07:27:18 EST 
Some errors clearly depend on others. A very common example is

The import a.b.c.Clazz cannot be resolved

Any usage of Clazz in that class will result in yet another error, which is in many cases resolved with the resolution of the wrong import.

Here an option to ignore theses dependent errors would lead to clearer error reports.
Comment 1 Eclipse Genie CLA 2020-09-13 11:32:40 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Marvin Fröhlich CLA 2020-09-14 02:29:28 EDT 
No, the problem still persists.
Comment 3 Eclipse Genie CLA 2023-03-08 18:11:47 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.