Bug 30699 - External JAR: no refresh in JavaModel if full build occurred before
Summary: External JAR: no refresh in JavaModel if full build occurred before
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: 2.1 M5   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-31 05:32 EST by Philipe Mulet CLA
Modified: 2003-02-13 05:17 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 Philipe Mulet CLA 2003-01-31 05:32:24 EST 
Build 20030129

In the following situation, a (full) build will hamper the detection of 
external JAR updates even if explicitly invoked (refresh action).

1. Project P
  +- refers to missing external jar p1.jar

2. Observe no pkg root for p1.jar in package view (ok), CP marker in task view.

3. Go to file system, and add p1.jar at proper location

4. Back into Eclipse, trigger a rebuild all action, observe CP marker is gone.

5. Trigger 'refresh' action in package view, observe that the model isn't 
updated (still no root for p1.jar).
Comment 1 Jerome Lanneluc CLA 2003-02-03 11:17:29 EST 
Builder used to call getResolvedClasspath(...) which would cache the timestamps 
or external jars.

Changed it to cache the timestamps when the project is opened.
Comment 2 David Audel CLA 2003-02-13 05:17:23 EST 
Verified.