Community
Participate
Working Groups
When you have a problem due to an issue with your manifest file there is no decent way to filter them to find the root problem. Example 1) Get 3.2.1 2) Load org.eclipse.search from HEAD 3) There are 30 odd errors. The two that matter are two Unsatisifed Links which are lexically last so really hard to see
PDE markers have their own marker id. To filter for only PDE markers, in the problems view select the filter icon. On the right hand side of the Filters dialog, there is a checkbox tree with all available types. Click "Deselect All" and then check "PDE Problem". Click OK and you should see only markers coming from PDE. Hopefully this helps.
Wassim set me straight on what the bug was asking for. Sorry for the confusion. Reopening.
Brian & Wassim, what categories are you thinking of here? So far I have (modeled after JDT): Fatal Errors Deprecation Externalized Strings Thoughts?
The number one thing for me is the dependency errors that prevent you from doing anything else. They should be in a category on thier own (and it should be first) as all other errors are a side effect.
Created attachment 51393 [details] org.eclipse.pde.patch Please review for sanity Brian.
we have these categories: Fatal Errors Deprecation Execution Environment Externalized Strings Feel free to open other requests if you would like other categories :)