Bug 3191

Summary: JM - non-existing external jars will not come to life when created (1FWI5C4)
Product: [Eclipse Project] JDT Reporter: Darin Wright <darin.eclipse>
Component: CoreAssignee: Philipe Mulet <philippe_mulet>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: P3    
Version: 2.0   
Target Milestone: 2.0 M3   
Hardware: All   
OS: All   
Whiteboard:

Description Darin Wright CLA 2001-10-10 22:51:01 EDT 
DW (6/13/00 4:14:43 PM)
	If you have a classpath entry to an external jar that does not exist, and then you
	create the jar, the jar will never be noticed by the Java Model (although the
	builder will likely notice it).

	Since we get no deltas for such resources we can never discover the file.

PM (6/9/2001 3:01:16 PM)
	Maybe next time we build, we could force to refresh the JavaModel if noticing the JAR is available... unclear.
Comment 1 Philipe Mulet CLA 2001-10-11 09:21:49 EDT 
Should investigate this one in the context of extension directories.
Comment 2 Philipe Mulet CLA 2002-02-07 07:43:23 EST 
We force a classpath marker refresh when building or on a prebuild change (if 
autobuild is turned off), this will take care of this one.

Closing