Bug 3304 - Hierarchy not updated when changing classpath (1GF5QSW)
Summary: Hierarchy not updated when changing classpath (1GF5QSW)
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P3 critical (vote)
Target Milestone: 2.0 M2   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 22:52 EDT by Jerome Lanneluc CLA
Modified: 2002-01-11 09:34 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jerome Lanneluc CLA 2001-10-10 22:52:54 EDT
TM (6/11/2001 15:10:11)	
	SDK 122

	1) smoke test setup
	2) move the package junit.extensions to a newly created java project foo
	3) put the JUnit project on the classpath of foo
	4) open a class hieararchy on ExceptionTestCase
	5) observe: the type hieraryh now shows ExceptionTestCase as a subclass of Object
	6) put JUnit back on the classpath of foo.
	7) observe: no update of the type hierarchy happens.

EG (7/12/01 11:17:45 AM)
	are we getting the proper notifications from JCORE

MA (03.08.2001 11:50:49)
	Missing change notifications from the ITypeHierarchy
	Same when a CU is same project:
		1. CreateCU X.java
			public class X extends C {
			}
			class C {
			}
		2. Open type hierarchy on X
		3. rename C -> C1 (by editing)
			-> no type hierarchy change notification
		4. rename C1 -> C
			-> no type hierarchy change notification
	2 CU's in the same file
		1.	X.java
			public class X extends Y {
			}
			Y.java
			public class Y {
			}				
		2. Open type hierarchy on X
		3. Rename Y -> Y1
			-> type hierarchy change notification
		4. rename Y1 -> Y
			-> no type hierarchy change notification

	Move to JCore
Comment 1 Jerome Lanneluc CLA 2001-10-24 06:53:18 EDT
Fixed first case, i.e. rename a type so that its subtype has an invalid 
supertype.

Need to fix second case. To do so, need to rewrite TypeHiearchy.isAffectedByType
(...) to use names instead of handles.
Comment 2 Jerome Lanneluc CLA 2002-01-10 13:15:43 EST
Implemented mechanism that remember the simple names of the missing types of a 
hierarchy. When a type is added, it now looks in this list to see if the 
hierarchy needs refresh.