Community
Participate
Working Groups
This is related to Europa release. Mylar project recently introduced Task working sets that operate on something that has nothing to do with resources. However, those task working sets appear in the "Open Resource" dialog drop down and when Window working set is only including task working set "Open Resource" dialog don't show any hits at all. Also, even if I pick "No working set" option in the "Open Resource" dialog it still show no hits, like it is actually using "Window working set". So, I believe there is a bug in the filtering code that deal with working sets in the "Open Resource" dialog. Also, it would make sense to filter out non-resource working sets from the "Open Resource" dialog UI, since those won't do any good there.
Is there are chance that this issue will be addressed for 3.3 release (Europa)? Also note that the same issue can be reproduced using Breakpont working sets contributed by Platform/Debug (or JDT). So, Open Resource dialog finds nothing if Window working set has Breakpont working set selected.
This problem in the description turned out to be that the Mylyn TaskWorkingSetPage.performFinish() was adding all adaptables instead those matching AbstractTaskContainer (bug 189308). This was effectively making the task working sets function like resource working sets that contained no resources. So if a particular facility (e.g. Open Resource, Package Explorer) had no other resource working sets selected it would not show any resources.
I made a mistake in the diagnosis described in comment#2. I had nothing in the Breakpoint working set that I was testing this with, and the Open Resource dialog's working set filtering mechanism has a special case that if the only working set is empty it will set the working set to filter on to be null instead of the Window Working Set. I created bug 193047 to desribe the root problem and steps to reproduce. Reopening this bug open because it might make sense to make a fix or work-around for the Open.
Reassigning to Susan.
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
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.
