Bug 38607

Summary: Refresh does not capture changes in jar files
Product: [Eclipse Project] JDT Reporter: Matthew King <matt>
Component: CoreAssignee: JDT-Core-Inbox <jdt-core-inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: P3    
Version: 2.1   
Target Milestone: 3.0 M2   
Hardware: PC   
OS: Windows 2000   
Whiteboard:

Description Matthew King CLA 2003-06-06 16:29:33 EDT 
Using Eclipse 2.1 integration build from 5/28. If you replace a jar file in the 
file system and then refresh that file from the navigator, changes in the jar 
file are not reflected in the package explorer or build path until Eclipse is 
closed and restarted.

Steps to reproduce:

1. Open a project that includes a jar on the build path, let's call it 
jarfile.jar.

2. In the file system, I was using Windows Explorer, replace jarfile.jar with a 
new version, same name, but modified contents, e.g., add a package, class, or 
method in an existing class. 

3. Open the java perspective and the package explorer.

4. Navigate to jarfile.jar Notice that the changes in jarfile.jar are not 
visible.
Comment 1 Philipe Mulet CLA 2003-06-06 16:59:13 EDT 
External files are not monitored by Eclipse. In the package view, JDT 
explicitly checks referenced external files using the refresh action (in 
package view uniquely).

Does this latter work for you ? Refresh shouldn't be so much context 
sensitive...
Comment 2 Philipe Mulet CLA 2003-06-10 06:43:16 EDT 
Closing, please reopen if package view refresh doesn't work for you.