Bug 30697

Summary: Classpath marker update could trigger automatic refresh for external JARs
Product: [Eclipse Project] JDT Reporter: Philipe Mulet <philippe_mulet>
Component: CoreAssignee: Jerome Lanneluc <jerome_lanneluc>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: 2.1   
Target Milestone: 2.1 M5   
Hardware: PC   
OS: Windows 2000   
Whiteboard:

Description Philipe Mulet CLA 2003-01-31 05:17:22 EST 
Build 20030129

When the builder kicks in and notices some missing JAR got added (or 
reciprocally), it could inform the JavaModel so that during the next 
POST_CHANGE notification it will automatically refresh external JAR status (as 
can be done using the JavaModel API manually).

This would make our behavior much more consistent.
Comment 1 Jerome Lanneluc CLA 2003-02-03 11:15:42 EST 
Changed the 2 methods on the Java builder that update the markers 
(JavaBuilder.isWorthBuilding() and BatchImageBuilder.build()) to notify the 
delta processor that external jars need to be refreshed.
Comment 2 David Audel CLA 2003-02-13 05:23:56 EST 
Verified.