Bug 128217 - Grouping all fatal problems together
Summary: Grouping all fatal problems together
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.2 M6   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-16 10:33 EST by Philipe Mulet CLA
Modified: 2006-03-27 08:56 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 Philipe Mulet CLA 2006-02-16 10:33:13 EST 
Version: 3.2.0
Build id: I20060215-0010

The support for categorizing problems should offer to group all fatal errors into the same category, so as to emphasize their severity.

If option 'treat configurable errors like fatal errors' is enabled (as it is by default), some optional errors are becoming fatal; i.e. code is no longer executable.

e.g. when treating configurable errors like fatal errors, then an access restriction pb for a non-accessible type should be categorized as fatal. If treating configurable errors as not fatal, then the problem should be categorized under 'access restrictions'.
Comment 1 Philipe Mulet CLA 2006-02-17 11:50:09 EST 
Fixed (>M5).
Comment 2 David Audel CLA 2006-03-27 08:56:26 EST 
Verified for 3.2 M6 using build I20060327-0010