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

Bug 91037

Summary:	[hierarchy] type parameter change could invalidate type hierarchy
Product:	[Eclipse Project] JDT	Reporter:	Philipe Mulet <philippe_mulet>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.1
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Philipe Mulet

2005-04-11 14:52:40 EDT

Build 3.1m6

Adding/removing a type parameter could change the supertype relation chain,
since a type parameter may shadow an outer type.

e.g.

class X extends List<String>

==>

class X<List> extends List<String>

Comment 1 Jerome Lanneluc

2007-06-22 10:59:41 EDT

To reproduce:
1. Create the following CU:
import java.util.ArrayList;
public class X extends ArrayList<String> {
}
2. Create a type hierarchy on X
3. Change the CU to:
import java.util.ArrayList;

public class X<ArrayList> extends ArrayList<String> {
}
Observe: the hierarchy is not updated
If you close the Hierarchy view and reopen the hierarchy on X, then the Hiearchy  view correctly show that X has no super type since its hierarchy is broken.

Comment 2 Jerome Lanneluc

2008-05-07 18:23:33 EDT

Deferring post 3.4

Comment 3 Eclipse Genie

2020-03-06 16:21:16 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.