Community
Participate
Working Groups
The change in bug 550183 breaks the case when there is a p/my/SomeClass.class and p/my/SomeClass/someResource.txt in the same project (but different source folders, if that makes any difference). Jenkins code uses that approach for a huge lot of different resources. In this case it should be a warning. At the very least, this problem's severity needs to be configurable on project level (there is a bug 377850 for that).
This issue was reported and fixed in bug #163807 from 2006. Bug #377850 was reported in 2012 which suggests there was a regression. This bug from 2019 also notes the regression, pointing to changes in bug #550183 (also from 2019) as the cause of the regression. Looking back at bug #377850, there was activity in 2020 which claims that the issue was fixed. Bug #571218 shows that the bug is still present, with a link to a minimal example project to reproduce.
*** Bug 571218 has been marked as a duplicate of this bug. ***
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.
