Bug 100839 - [type hierarchy] Type hierarchy: lock mode should not based type variable interpretation of project settings
Summary: [type hierarchy] Type hierarchy: lock mode should not based type variable int...
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.2 M1   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-20 11:03 EDT by Dirk Baeumer CLA
Modified: 2005-12-13 05:28 EST (History)
1 user (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 Dirk Baeumer CLA 2005-06-20 11:03:19 EDT 
RC3

- create a new workspace
- use a 1.5 JDK as a default
- open HashMap
- put cursor on put
- open quick type hierarchy

observe: the sub class ProcessEnvironment doesn't show up although it overrides
put. The problem is that the type variable interpretation is only done if the
compiler compliance level is 5.0. However since both classes come from the JRE
the interpretation has to be done as well.

The problematic code is in: JavaModelUtil#getParameterTypes.
Comment 1 Dirk Baeumer CLA 2005-06-20 11:04:45 EDT 
This can get even more annoying in a scenario where two projects share the same
JRE but have different compiler compliance level. If the rt.jar is first opened
from a 1.4 JDK the override computation will even fail for a project having 5.0
compliance.

Martin, can you please investigate how risky a fix would be ?
Comment 2 Dirk Baeumer CLA 2005-09-10 13:33:27 EDT 
This got fixed. Tested on I20050906-1200
Comment 3 Benno Baumgartner CLA 2005-12-13 05:25:46 EST 
verifing...