Bug 538118 - Warning icons are no longer propagated in project explorer
Summary: Warning icons are no longer propagated in project explorer
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.8   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-21 07:30 EDT by Michael N. Lipp CLA
Modified: 2022-09-22 11:45 EDT (History)
1 user (show)

See Also:

Attachments
Screenshot from project explorer (6.65 KB, image/png)
2018-08-21 07:30 EDT, Michael N. Lipp CLA 		no flags Details
View All 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 Michael N. Lipp CLA 2018-08-21 07:30:36 EDT 
Created attachment 275468 [details]
Screenshot from project explorer

Before Photon, if one of my Java sources had a warning, the warning "add-on" to the usual icon was shown in the project explorer for
(1) the source file
(2) the package
(3) the folder (src)
(4) the project
(5) the containing project

Starting with photon, the propagation stops at the folder level. This is very annoying because I now have to expand each project in order to check if warnings remain to be fixed.
Comment 1 Eclipse Genie CLA 2020-08-27 17:48:59 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 Eclipse Genie CLA 2022-09-22 11:45:12 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.