Bug 43872 - Hierarchy does not update properly when local class eliminated [type hierarchy]
Summary: Hierarchy does not update properly when local class eliminated [type hierarchy]
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 M4   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-29 17:15 EDT by Nick Edgar CLA
Modified: 2003-10-13 05:47 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Edgar CLA 2003-09-29 17:15:37 EDT
build I20030927

- open hierarchy on ViewerSorter
- change ViewerSorter to be non-abstract and have public constructors
- select first "Anonymous of ViewerSorter" subclass (in ProjectReferencePage)
- change it to call the 0-arg constructor, rather than creating an anonymous 
subclass
- save
- the hierarchy updates to show "Anonymous of ICheckStateListener", which is 
the next anonymous class in ProjectReferencePage
Comment 1 Nick Edgar CLA 2003-09-29 17:16:44 EDT
If there is no subsequent anonymous class, the label in the hierarchy becomes 
blank.
Comment 2 Dirk Baeumer CLA 2003-09-29 17:24:44 EDT
Martin, this is a know JDT core limitation in M4. Right ?
Comment 3 Martin Aeschlimann CLA 2003-09-30 13:46:38 EDT
Was able to reproduce.
It seems that the type hierarchy does not get notified that it changed.
The hierarchy still reacts to the Java element delta and refreshes. The label
gets empty as the type does not exist any more. If there is a subsequest
anonymous type the handle is still able to resolve as the two types are equal in
the model.

Moving to jdt.core
Comment 4 Jerome Lanneluc CLA 2003-10-01 07:10:28 EDT
Added support in TypeHierarchy to handle local and anonymous type changes.
Comment 5 David Audel CLA 2003-10-13 05:47:23 EDT
Verified.