Summary: | Libraries in build path are locked by Eclipse | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Uwe Klosa <uwe.klosa> |
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 3.0.1 | ||
Target Milestone: | 3.1 M5 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Uwe Klosa
2004-12-07 12:59:50 EST
Pls provide steps to reproduce. Also, is this occurring in latest 3.1 stream as well ? 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 If you select the Java project and refresh it (F5), is the external jar content refreshed ? No. I have tried that, too. If the timestamp of the external jar changes, hitting refresh on its Java project (in the Package Explorer) updates its content for me. Well, it can be some configuration on my workstation. I will test it again. Please reopen if you can reproduce and if you have steps to reproduce. |