Bug 3191 - JM - non-existing external jars will not come to life when created (1FWI5C4)
Summary: JM - non-existing external jars will not come to life when created (1FWI5C4)
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 2.0 M3   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 22:51 EDT by Darin Wright CLA
Modified: 2002-02-11 06:46 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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