Bug 5831 - Opening a type hierarchy on a small project is slooow
Summary: Opening a type hierarchy on a small project is slooow
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P1 normal (vote)
Target Milestone: ---   Edit
Assignee: Martin Aeschlimann CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 5820
  Show dependency tree
 
Reported: 2001-11-13 03:36 EST by Erich Gamma CLA
Modified: 2001-11-19 11:59 EST (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 Erich Gamma CLA 2001-11-13 03:36:29 EST 
1) self hosting workspace
2) select JUnit project in packages view
3) execute "Open Type Hierarchy" from the context menu.
->it takes minutes until the hierarchy shows up.
The hierarchy is the full hierarchy of Object and not the hierarchy scoped to 
JUnit.
Comment 1 Erich Gamma CLA 2001-11-13 04:38:26 EST 
As an aside the VM size went up from 40 to 162MB.
Comment 2 Martin Aeschlimann CLA 2001-11-19 11:59:23 EST 
Opening a type hierarchy on a project now builds a hierarhcy that contains only 
the elements in source folder (no elements from JARs).

fixed in 11116