Summary: | [type hierarchy] Hierarchy view fails to pick up class modifier change | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Tim Ellison <t.p.ellison> | ||||||
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> | ||||||
Status: | CLOSED FIXED | QA Contact: | |||||||
Severity: | normal | ||||||||
Priority: | P3 | CC: | martinae | ||||||
Version: | 3.0 | ||||||||
Target Milestone: | 3.1 RC2 | ||||||||
Hardware: | PC | ||||||||
OS: | Windows 2000 | ||||||||
Whiteboard: | |||||||||
Attachments: |
|
Description
Tim Ellison
2004-06-04 12:26:00 EDT
Not critical for 3.0 Problem still exists in 3.1M4 The problem is that (for performance reasons) we use cached flags offered by the type hierarchy. Unless the type hirarchy is refreshed, the flags will be the same. Either the type hierarchy gives a change notification whenever a modifier changes, or we accept this bug and show the flags as they were when the hierarchy was created. The second take is ok for me. Moving to jdt.core to decide Created attachment 21891 [details]
Proposed fix
Created attachment 21892 [details]
Regression test
+1 for RC2 Released fix and test. Verified in N20050606-0010. Verified for 3.1 RC2 using build I20050610-0010 |