Bug 495375 - [call hierarchy] Changing search scope to working set removes all entries
Summary: [call hierarchy] Changing search scope to working set removes all entries
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.5.2   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Noopur Gupta CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2016-06-03 06:31 EDT by Rüdiger Herrmann CLA
Modified: 2016-06-21 01:11 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rüdiger Herrmann CLA 2016-06-03 06:31:20 EDT 
Steps:
1. Working set called 'foo' containing a 'org.example.foo' project
2. Open call hierarchy for Job.setRule()
3. Wait till search is done, some callers are in 'org.example.foo'
4. Narrow search scope to the 'foo' working set
5. The tree is empty, except for the 'setRule()' entry
=> should display only callers from the 'foo' working set
Comment 1 Dani Megert CLA 2016-06-03 06:44:25 EDT 
Noopur, please have a look.
Comment 2 Noopur Gupta CLA 2016-06-07 09:16:09 EDT 
I am not able to reproduce it with the steps given in comment #0 on Windows 7. Changing the scope via the view menu correctly shows the callers from only the selected working set.

Please try with
http://download.eclipse.org/eclipse/downloads/drops4/S-4.6RC4a-201606061100/

and provide more details. Also attach the sample project if that helps to reproduce the issue.
Comment 3 Rüdiger Herrmann CLA 2016-06-20 14:05:53 EDT 
(In reply to Noopur Gupta from comment #2)
> I am not able to reproduce it with the steps given in comment #0 on Windows
> 7. Changing the scope via the view menu correctly shows the callers from
> only the selected working set.
> 
> Please try with
> http://download.eclipse.org/eclipse/downloads/drops4/S-4.6RC4a-201606061100/
> 
> and provide more details. Also attach the sample project if that helps to
> reproduce the issue.

I am afraid, I cannot reproduce the problem with an example setup and the latest build. From my POV, the bug can be closed. I will reopen it if I eventually find a way to reproduce it.