Bug 80394 - Libraries in build path are locked by Eclipse
Summary: Libraries in build path are locked by Eclipse
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.1 M5   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-07 12:59 EST by Uwe Klosa CLA
Modified: 2005-01-24 12:02 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 Uwe Klosa CLA 2004-12-07 12:59:50 EST 
Libraries that are in the build path of my Java projects are locked by Eclipse
and any external updating of these libraries can not be seen of all other
applications.

In our team we are using one central filder for the libraries we do need in our
projects. When I have started Eclipse and one of the libraries is updated can
this not be recognized by any application on my workstation. First after closing
Eclipse the libraries are unlocked and all updates can be recognized.
Comment 1 Philipe Mulet CLA 2004-12-08 09:47:10 EST 
Pls provide steps to reproduce. Also, is this occurring in latest 3.1 stream as
well ?
Comment 2 Uwe Klosa CLA 2004-12-08 10:34:33 EST 
I have talked about that problem with another developer and he thinks it might
be a problem with java on Windows. But here the steps for reproducing:

OS: Windows XP SP2
Java: Sun SDK 1.4.2_05
Eclipse: 3.0.1 Build id: 200409161125
JDT: 3.0.1 200409161125

1. Create a java project.
2. Add under build path / libraries an external jar from a network folder and
click on OK.
3. Do not close Eclipse. Update this jar file on the server with another version
where you can see easily it is another version.
4. You will see in Explorer on your workstation that the timestamp of the jar
file has changed. But have a look into it. Do you see the new content or still
the old content.
5. If you close Eclipse you will see the new content.

This problem only occurs with external jars and I have not tested Eclipse 3.1
Comment 3 Jerome Lanneluc CLA 2004-12-08 10:38:24 EST 
If you select the Java project and refresh it (F5), is the external jar content
refreshed ?
Comment 4 Uwe Klosa CLA 2004-12-08 10:45:06 EST 
No. I have tried that, too.
Comment 5 Jerome Lanneluc CLA 2004-12-08 10:50:03 EST 
If the timestamp of the external jar changes, hitting refresh on its Java
project (in the Package Explorer) updates its content for me.
Comment 6 Uwe Klosa CLA 2004-12-08 11:31:43 EST 
Well, it can be some configuration on my workstation. I will test it again.
Comment 7 Jerome Lanneluc CLA 2005-01-24 12:02:50 EST 
Please reopen if you can reproduce and if you have steps to reproduce.