Bug 18331

Summary:	Java Model not flushed when upgrading binary projects
Product:	[Eclipse Project] JDT	Reporter:	Randy Hudson <hudsonr>
Component:	Core	Assignee:	Kent Johnson <kent_johnson>
Status:	VERIFIED FIXED	QA Contact:
Severity:	major
Priority:	P3
Version:	2.0
Target Milestone:	2.0 F2
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description Randy Hudson

2002-05-30 11:37:56 EDT

I had 0521 build imported (org.eclipse.ui + pre-reqs only) as binary projects.  
I then turned off auto-build, deleted the projects (and directories), and 
imported 0529 (org.eclipse.ui+required again) as binary project.

I was doing this because the internal Type SafeRunnableAdapter was removed.  
After turning on auto-build, I was still able to find SafeRunnableAdapter in 
the Type selection dialog.  When I opened it, it was a RED icon and the type 
did not exist.  It also showed up in the ISafeRunnable Hierarchy View, again 
with a RED icon.

Comment 1 Randy Hudson

2002-05-30 11:41:06 EDT

Update:
Actually, when using the open dialog I get "Could not uniquely map the name to 
a type".

I deleted org.eclipse.ui again, this time with auto-build enabled, and re-
imported.  the model is still stale.

Comment 2 Philipe Mulet

2002-05-30 11:54:37 EDT

Randy, could you give it a try with 20020529 ? We released in there a couple 
changes which should have solved this scenario.

Comment 3 Jerome Lanneluc

2002-05-31 12:07:08 EDT

Indexes for jars in the project where not removed when a project was deleted.

Fixed.

Comment 4 Kent Johnson

2002-06-03 11:55:44 EDT

Verified.