Community
Participate
Working Groups
Dialog 'Configure Contents' of the Problems-View: it would be very nice, if the contents of the problem view could be filtered by than just the description. Especially 'path' would be useful for filtering away third-party or generated source-code.
You can use the Scope filter and workingsets to achieve this.
How exactly? As far as i see, this only works, if the to-be-filtered source is in another project. If it resides in the same project, working-sets do not help. Example: think of two source-folders in the same project, 'src' and 'srcbind', the latter containing source generated by JAXB. The 'srcbin' folder will always contain many warnings, oblitering the real warning from 'src'. Of course, you could set the scope to selected only (i.e. the 'src' folder), but in this case you miss the general warning from the project itself (i.e MANIFEST.MF etc.) and it does not work when selecting several projects at once.
Hmm. Given your usecase of excluding a few specific resources, I get it. Thanks for the details.Will look into this for 3.6.
Great, Thanks!
I can think of : 1. Adding a finer way of selecting from workingset scope.( On contained resources and its children). This should allow you to create workingsets with just the project folder itself, manifest.mf,etc.And another one for the other projects and src. 2. Or less likely, an exclusion filter for scope. This would add to the size of the dialog and require some rework.
Hm, 1. sound still a bit complicated (defining all these detailed working-set for bigger projects). If 2 is too unlikely, why not just add a line below description (Description contains/doesn'tcontain <some pattern>) for the path of the marker (Path contains/doesn'tcontain <another pattern>)?
Hitesh, you should set the milestone to 3.6 if you intend to work on this.
*** Bug 275453 has been marked as a duplicate of this bug. ***
See Bug 293061.
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.
