Bug 488327 - disable fatalOptionalErrors in our code
Summary: disable fatalOptionalErrors in our code
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.6   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-02-23 12:51 EST by Stephan Herrmann CLA
Modified: 2022-06-03 17:35 EDT (History)
1 user (show)

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 Stephan Herrmann CLA 2016-02-23 12:51:48 EST 
I'd like to leverage bug 479303, mostly I have this use case:

- I want to test the difference made by a certain code block, so I comment the block and run tests.

- Then I notice that by commenting, an import became unused => error

Since bug 479303 this shouldn't block running tests, except that bug 479303 respects the option fatalOptionalErrors, so I'm back at square one, where for each such experiments imports unnecessarily have to be "organized".

Therefor I'm suggesting we switch fatalOptionalErrors to disabled.

If there's any error (optional or mandatory) this will fail the build anyway, so no danger we'd ever ship such code, right?
Comment 1 Manoj N Palat CLA 2017-05-25 00:24:37 EDT 
moving to 4.8
Comment 2 Manoj N Palat CLA 2018-05-16 01:38:24 EDT 
Bulk move out of 4.8
Comment 3 Eclipse Genie CLA 2020-06-01 20:05:43 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 4 Eclipse Genie CLA 2022-06-03 17:35:17 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.