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

Bug 161035

Summary:	[hierarchy][resilisnece] Inconsistent handling of missing member super types
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.3
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Philipe Mulet

2006-10-16 07:50:40 EDT

Build 3.3M2

HierarchyResolver#findSuperInterfaces(...) extracts the simple name (after last dollar sign) to inject in collection of missing types.

HierarchyResolver#findSuperclass(...) does not. This is inconsistent.

BTW: one alternative could be to always record the entire dollar simple name (eg. Map$Entry), and have the invalidation check for possible matches on trailing portion:

ie. Map$Entry would match change on Map$Entry or Entry

Comment 1 Philipe Mulet

2006-10-16 07:55:34 EDT

Also should check where superInterface is a missing binary type (see bug 114349).
findSuperclass(...) has been upgraded, but not findSuperInterfaces(...)

Comment 2 Jerome Lanneluc

2008-05-12 05:25:28 EDT

Deferring post 3.4

Comment 3 Eclipse Genie

2020-04-09 09:15:13 EDT

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.