Bug 12496 - Creating a type hierarchy should not populate java model cache
Summary: Creating a type hierarchy should not populate java model cache
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.1 M1   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-03-29 05:00 EST by Jerome Lanneluc CLA
Modified: 2002-09-10 08:51 EDT (History)
0 users

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 Jerome Lanneluc CLA 2002-03-29 05:00:31 EST 
Build 20020328

When a type hierarchy is created, a SearchNameEnvironment is used. This 
unnecessarily populates the java model cache (most types will never be even 
looked at by the user). We should use a FileNameEnvironment in this case.
Comment 1 Philipe Mulet CLA 2002-03-29 06:15:34 EST 
What about hierarchy which are often refreshed ? Same for supertype only 
hierarchies ? (used to decorate method in outliner)
Comment 2 Jerome Lanneluc CLA 2002-05-07 09:55:15 EDT 
Yes, this change is too risky at this point of the release. Deferring post 2.0.
Comment 3 Philipe Mulet CLA 2002-07-25 06:59:39 EDT 
Reopening
Comment 4 Philipe Mulet CLA 2002-07-25 07:00:56 EDT 
Clearing resolution
Comment 5 Philipe Mulet CLA 2002-07-25 07:34:14 EDT 
Is it still an issue ?
Comment 6 Jerome Lanneluc CLA 2002-08-27 06:42:17 EDT 
No, this is not an issue any longer.
Closing.