Bug 215098 - [search] Search references does not work when call is not directly (XX.getInstance().thisMethod())
Summary: [search] Search references does not work when call is not directly (XX.getIns...
Status: VERIFIED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.4   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 3.4 M5   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-11 18:59 EST by arie CLA
Modified: 2008-02-05 05:52 EST (History)
3 users (show)

See Also:

Attachments
No references (not even myself - the caller). (59.17 KB, image/png)
2008-01-11 18:59 EST, arie CLA 		no flags Details
View All 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 arie CLA 2008-01-11 18:59:58 EST 
Created attachment 86739 [details]
No references (not even myself - the caller).

Build ID: I20071213-1700

Steps To Reproduce:



More information:
Search references (or any kind of Java search) does not work for me when checking thisMethod: XXX.getInstance().thisMethod().
See attached screenshot. Should I have at list one reference call (my self)?
Comment 1 Frederic Fusier CLA 2008-01-14 10:56:08 EST 
Sounds more like a JDT/Core issue, but I can't reproduce with a simple test case.
Can you isolate a simple test case in your workspace which reproduces this problem?
Comment 2 arie CLA 2008-01-14 13:47:48 EST 
I can't reproduce it myself now (using the same case or a different example).
I did restart eclipse since then.
BTW, the two sources were located in 2 different src folders.
Comment 3 Frederic Fusier CLA 2008-01-15 07:21:05 EST 
I also got it once after having created a second source folder and move the class which has the reference. I also close and restart and the problem vanishes.
I tried to redo my first steps but always failed to reproduce it...

Did you also move the class one source folder to the other one before having noticed this problem?
Comment 4 arie CLA 2008-01-15 14:31:44 EST 
Actually, yes.
Comment 5 Frederic Fusier CLA 2008-01-15 15:21:29 EST 
So, it looks like the indexer was not updated while moving the file between the two source folders. But as it's hard to reproduce, it guess it should be a timing issue and then, that will be a little bit tricky to catch it up...
Comment 6 Frederic Fusier CLA 2008-01-17 09:42:24 EST 
OK, as we cannot reproduce on both sides, I close this bug as WORKSFORME for now. Of course feel free to reopen if you get it again, hopefully with a reproducible test case, thanks
Comment 7 Maxime Daniel CLA 2008-02-05 05:30:53 EST 
(In reply to comment #3)
> I also got it once...
Wouldn't that call for another resolution?
Comment 8 Maxime Daniel CLA 2008-02-05 05:52:07 EST 
After discussing the issue with Frédéric, it occurs that he has made extensive attempts to reproduce the problem, and a single one succeeded (not even the last one). While making this bug a WORKSFORME departs from the 'we could never reproduce it' line, it sounds reasonable to adopt it until we find a more reproductible test case.

Verified for 3.4 M5.