Summary: | [WorkingSets] Support working set exclusion | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Andrew McCullough <mccull1> |
Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P5 | CC: | dcorbin, douglas.pollock, knut_radloff, noelgrandin, Tod_Creasey |
Version: | 2.0 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Andrew McCullough
2002-08-12 13:43:56 EDT
This would be a matter of having different filter options for those views that support working sets. Any working set could be selected as either an inclusive or exclusive working set. Tagging as tasks because that would be the first and most important candidate for supporting exclusive working set filters. Navigator should also consider implementing this, if Tasks does. Additional Use Case: I turn on some additional compiler checks to catch dubious code in my project. Unfortunately, I have tons of generated java files that also triggers those checks. I want to be able to say "this working set excludes files that match the following pattern" much as I can do in the package explorer filter. Note that this feature request is still open against 3.0M9. *** Bug 46450 has been marked as a duplicate of this bug. *** There are currently no plans to work on this feature This seems like a valid feature request. Given that other people showed interest I think this should preferably be marked resolved/later. Unless there is a good reason why this should not be addressed. I agree with Knut's comment 6. WONTFIX means nobody will ever look at this again. LATER means it will still show up on the "maybe" radar. reopening I have run into this problem as well. Generated code or code that is included for compliance with a framework can lead to unwanted markers in the Problems view. It also is easier to visualize the source under development if generated or 3rd party code is excluded from various views (e.g., Package Explorer). This defect may be addressed under a general working set refresh but there are no concrete plans at this time. 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. |