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

Bug 394957

Summary: Type hierarchy incomplete
Product: [Eclipse Project] JDT Reporter: Doug Simon <doug.simon>
Component: CoreAssignee: Jesper Moller <jesper>
Status: VERIFIED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: anchakrk, jarthana, srikanth_sankaran
Version: 4.2.1   
Target Milestone: 4.3 M6   
Hardware: Macintosh   
OS: Mac OS X   
Whiteboard:
Attachments:
Description Flags
incomplete Quick Type Hierarchy for ResolvedJavaType
none
Zipped up Java sources and Eclipse project files none

Description Doug Simon CLA 2012-11-23 04:15:16 EST 
Created attachment 223899 [details]
incomplete Quick Type Hierarchy for ResolvedJavaType

For some types in my project, an incomplete type hierarchy is shown in both the Type Hierarchy view as well as in the Quick Type Hierarchy view. Unfortunately I cannot reproduce a small test case. However, checking out the code and reproducing the problem is fairly straightforward:

hg clone http://hg.openjdk.java.net/graal/graal
cd graal
mxtool/mx ecl  # requires Python 2.7 tobe on PATH

Start Eclipse with new workspace directory being graal.
Configure a JDK1.7 as the default JRE.
File | Import... | General | Existing Projects into Workspace
Choose graal/graal subdirectory and import all discovered projects.

Open type ResolvedJavaType and shows its type hierarchy. It will only show HotSpotTypePrimitive (see attachment) but it should also show HotSpotResolvedJavaType.

This behaviour also occurs in 4.3 but not in 3.8.1.
Comment 1 Jay Arthanareeswaran CLA 2012-11-28 03:39:43 EST 
I am having trouble with cygwin and python 2.7. It would be better if you can just isolate the issue and share the test case. TIA!
Comment 2 Doug Simon CLA 2012-11-28 04:45:06 EST 
Created attachment 224039 [details]
Zipped up Java sources and Eclipse project files
Comment 3 Doug Simon CLA 2012-11-28 04:47:57 EST 
Sorry, I know the Graal development set up is not so natural on Windows.

As a workaround, I have zipped up the sources including the Eclipse project files and attached it here. After unzipping, you should now be able follow my original instructions from "Start Eclipse with ..." onwards.
Comment 4 Jay Arthanareeswaran CLA 2012-11-28 05:20:37 EST 
(In reply to comment #3)
> Sorry, I know the Graal development set up is not so natural on Windows.
> 
> As a workaround, I have zipped up the sources including the Eclipse project
> files and attached it here. After unzipping, you should now be able follow
> my original instructions from "Start Eclipse with ..." onwards.

Thanks, I can reproduce this now.
Comment 5 Jay Arthanareeswaran CLA 2012-11-28 05:53:59 EST 
Looks like a duplicate of bug 393192.

*** This bug has been marked as a duplicate of bug 393192 ***
Comment 6 Srikanth Sankaran CLA 2013-03-06 16:37:59 EST 
Jesper, Thanks for capturing this scenario in a junit test.
Comment 7 Srikanth Sankaran CLA 2013-03-07 22:00:43 EST 
Please confirm this is indeed a duplicate of bug 393192 and that the issue is 
resolved. If there is something unique about the test case, we want to capture
it as a junit.
Comment 8 Jesper Moller CLA 2013-03-08 16:50:48 EST 
Yes, this one is fixed as duplicate as well, the HierarchyResolver came across the three ingredients it needed: 10+ annotations, javadoc error which is suppressed, and finally a package-info.java.

Doug, thank you for reporting and supplying test files, good luck with Graal -- looks interesting.

*** This bug has been marked as a duplicate of bug 393192 ***
Comment 9 ANIRBAN CHAKRABORTY CLA 2013-03-12 05:05:05 EDT 
Verified for build eclipse-SDK-I20130310-2000 M6