Bug 7144 - Hierarchy incorrect when using binary projects
Summary: Hierarchy incorrect when using binary projects
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P2 normal (vote)
Target Milestone: 2.0 M3   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-20 12:48 EST by Nick Edgar CLA
Modified: 2002-01-18 12:31 EST (History)
0 users

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 Nick Edgar CLA 2001-12-20 12:48:50 EST 
Build 20011219

I have the SDK plugins in my workspace as binary self-hosting projects.
I have only org.eclipse.ui as source.

- open type on VMPreferencePage (in JDT debug UI)
- it takes a while, then the hierarchy shows just Object
- open type on TemplatePreferencePage (also in JDT debug UI)
- the hierarchy shows PreferencePage / TemplatePreferencePage (but not Object)
Comment 1 Dirk Baeumer CLA 2002-01-10 09:01:12 EST 
Martin, please investigate.
Comment 2 Martin Aeschlimann CLA 2002-01-11 06:21:48 EST 
reproducable with 20109. as described: All in binary except eclipse.ui
The hierarchy of TemplatePreferencePage (jdt.ui) has no super type.
(should be PreferencePage of eclipse.ui)

move to jdt.core
Comment 3 Jerome Lanneluc CLA 2002-01-18 05:50:11 EST 
TemplatePreferencePage was found to be outside the hierarchy because it's 
superclass binding was not computed at the time we ask.

Changed HiearchyResolver to eliminate the types outside the hierarchy just 
before reporting the hierarchy to the hierarchy builder (i.e. after all 
bindings have been resolved).
Comment 4 Nick Edgar CLA 2002-01-18 09:55:10 EST 
The other day I ran into a case where it couldn't resolve the hierarchy, and 
therefore couldn't do F3 or F4 when I had selected a type name.
It would be good to do the VA/Java-style cheat where if you have a capitalized 
word selected, it assumes it's a type name even if it can't be resolved, and 
does the same as Open Type on the name.
Comment 5 Jerome Lanneluc CLA 2002-01-18 10:17:47 EST 
Could you please enter a separate bug against open on selection?
Thanks.
Comment 6 Nick Edgar CLA 2002-01-18 12:31:11 EST 
Files bug 7891.