Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 552757

Summary: Call Hierarchy does not show all callers
Product: [Eclipse Project] JDT Reporter: Eike Stepper <stepper>
Component: UIAssignee: JDT-UI-Inbox <jdt-ui-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3    
Version: 4.14   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Attachments:
Description Flags
test.zip
none
Correct.zip
none
Incomplete.png
none
Incorrect.png
none
CDODevelopmentEnvironmentConfiguration.setup none

Description Eike Stepper CLA 2019-11-06 14:53:12 EST
For quite a while I have the problem that in my CDO workspace the Call Hierarchy (my favorite JDT tool) produces incomplete, sometimes wrong) results. I've spent the whole day to produce a stripped down stand-alone project to demo the effect. But I failed. At some point in the strip down process the problem always disappeared and all the correct results were displayed. I suspect that it relates to a complex interface inheritance structure.

Nevertheless I'll attach my most recent attempt to create this minimal example: test.zip. I'll also attach a few screenshots that show the Call Hierarchy results:

1) Correct.png shows the expected correct and complete results. The postCommit() method is called by two other methods. I only get this result with the stripped down version in test.zip.

2) Incomplete.png shows no callers of postCommit().

3) Incorrect.png shows a totally weird result. It seems that the second (expected) caller of postCommit() is shown under the first caller.

I fear the only way you can reproduce this problem is by checking out the CDO sources. To make this easier for you, in case you're interested, I'll attach a .setup file which you can simply drag to the Eclipse Installer, so that it creates the installation and workspace in mostly one click. I would really appreciate if you try it out, because the problem is really annoying for me and I know no other way to reproduce it. Please let me know if you need more instructions or help...
Comment 1 Eike Stepper CLA 2019-11-06 14:53:48 EST
Created attachment 280533 [details]
test.zip
Comment 2 Eike Stepper CLA 2019-11-06 14:54:22 EST
Created attachment 280534 [details]
Correct.zip
Comment 3 Eike Stepper CLA 2019-11-06 14:55:06 EST
Created attachment 280535 [details]
Incomplete.png
Comment 4 Eike Stepper CLA 2019-11-06 14:56:02 EST
Created attachment 280536 [details]
Incorrect.png
Comment 5 Eike Stepper CLA 2019-11-06 14:57:27 EST
Created attachment 280537 [details]
CDODevelopmentEnvironmentConfiguration.setup

Drag this file to the title area of the Eclipse Installer. Make sure you use the Advanced Mode of the installer.
Comment 6 Eike Stepper CLA 2019-11-07 02:08:22 EST
I found a much simpler way for you to reproduce the problem. To avoid confusion I close this bug and open bug 552774 with concise instructions...

*** This bug has been marked as a duplicate of bug 552774 ***