Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 344458 - Removing and adding back the same jar does not check file
Summary: Removing and adding back the same jar does not check file
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-02 10:10 EDT by Pascal Rapicault CLA
Modified: 2020-03-14 19:23 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal Rapicault CLA 2011-05-02 10:10:53 EDT
I20110428-0848

When I add a corrupted jar to the classpath, remove it from the classpath and replace it by a valid jar at the same location, the classpath container is not refreshed

Steps
- Add a corrupted jar (invalid zip) and notice the error on project
- Go on disk and replace the corrupted jar with a correct jar (same file name).
- Go to the Java Build Path properties, remove the entry, add it back from the same location, save.

You will notice that the project still has an error.
Comment 1 Eclipse Genie CLA 2020-03-14 19:23:58 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.