Community
Participate
Working Groups
Build ID: 3.4M5 The existing filters on the problems view allows to filter problems based on the contents of the problem description. It would be cool if it would be possible to filter based on other properties as well. For e.g. in my particular case, I have a lot of warnings in my code base, however I'm not concerned about warnings in junit test cases, so I could filter out all resources containing 'Test' in their resource name.
This is currently possible. Filter on description.
I'm not quite sure if I conveyed myself correctly. I would like to be filtering based on resource name in addition to the description. I'm willing to contribute a patch and hence reopening bug -- unless you strongly feel that this filter should not go into the eclipse problems view.
This should be pretty easy to contribute - just add a filter and a configuraration area to org.eclipse.ui.ide.resourceField in org.eclipse.ui.ide. See DescriptionConfigurationArea for a similar example
Great, will look into DescriptionConfigurationArea and file a patch.
"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"
Hello, I`m working untill one year with eclipse. It`s a nice IDE. But I have a Improvement-Idea: The displaying of Errors and Warnings can be configured. It will be nice, if I could select messages about his path. We work with generated and/or with ready Codeareas. Warnings in this codefiles are not interesting. But in the generated source we have more than 400 Warnings. So we don`t find the relevant Warnings. A filter like the Descriptionfilter about the path will be very helpful. As example we will selected „doesn`t contain“ „src-gen“. Best regardes Harald
(In reply to comment #6) > We work with generated and/or with ready Codeareas. Warnings in this codefiles > are not interesting. But in the generated source we have more than 400 > Warnings. So we don`t find the relevant Warnings. > > A filter like the Descriptionfilter about the path will be very helpful. > As example we will selected „doesn`t contain“ „src-gen“. If that is your use case, then you need this Bug# 220928