Bug 75816

Summary:	[search] Call Hierarchy does not find calls to the constructor of java.util.HashMap.Entry [call hierarchy]
Product:	[Eclipse Project] JDT	Reporter:	Michael Scharf <eclipse>
Component:	Core	Assignee:	Frederic Fusier <frederic_fusier>
Status:	VERIFIED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	markus.kell.r
Version:	3.0
Target Milestone:	3.1 RC1
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Michael Scharf

2004-10-07 12:06:25 EDT

- select the constructor of java.util.HashMap.Entry
- Call Hierarchy
==> the call hierarchy is empty (no calls found)

search in the file for "new Entry" and you will find several calls
to the constructor of Entry :-/

Problem found with eclipse 3.0.1

Comment 1 Markus Keller

2004-10-07 13:11:10 EDT

Moving to JDT/Core.

Searching for references or declarations of said constructor doesn't report any
matches in I200410050800 with j9n142-20040928a.

Comment 2 Frederic Fusier

2004-10-07 13:13:12 EDT


*** This bug has been marked as a duplicate of 75642 ***

Comment 3 Frederic Fusier

2004-10-07 13:22:15 EDT

Oooops, my fault... I thought it was against 3.1...

Comment 4 Frederic Fusier

2004-11-02 06:17:44 EST

BinaryIndexer stores HashMap$Entry/4 as key index for constructor reference
although constructor pattern is looking for Entry/4... no chance to find it in
index files!

Comment 5 Frederic Fusier

2005-03-14 15:08:24 EST

If time permit

Comment 6 Frederic Fusier

2005-05-25 07:09:53 EDT

Fixed and released in HEAD.

Add key on static inner class in index. This increases size of index files about
0.7% (on classic tests workspace) and have no significant impact on performances.

[jdt-core internal]
Changes done in AbstractIndexer.addConstructorReference(...).
Also upgrade DiskIndex.SIGNATURE

Test case added in JavaSearchBugsTests

Comment 7 Olivier Thomann

2005-05-26 21:56:19 EDT

Verified in I20050526-2000