Bug 45060 - Missing external jar prevents build, but jar still in Java model
Summary: Missing external jar prevents build, but jar still in Java model
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.0 M7   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-16 17:37 EDT by Jerome Lanneluc CLA
Modified: 2004-02-12 12:59 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 Jerome Lanneluc CLA 2003-10-16 17:37:16 EDT 
Build 20031015

(autobuild on)
1. Create Java project with source folder 'src'
2. Add external jar
3. Rename external jar on disk only
4. Add class X in src
Observe: The project cannot be built because of the missing jar but it is still 
present in the Package Explorer
Comment 1 Jerome Lanneluc CLA 2003-10-16 17:38:18 EDT 
JavaBuilder should force a full refresh of the external jars for a given 
project. Right now it just update the markers.
Comment 2 Jerome Lanneluc CLA 2004-01-13 12:50:23 EST 
Moved external jar refresh and classpath markers creation to DeltaProcessor.
Comment 3 David Audel CLA 2004-02-12 12:59:42 EST 
Verified for 3.0M7