Bug 104195 - [misc] "File has changed on FS" for class files in JAR after unzipping workspace
Summary: [misc] "File has changed on FS" for class files in JAR after unzipping workspace
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-18 04:07 EDT by Christof Marti CLA
Modified: 2023-12-08 18:59 EST (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 Christof Marti CLA 2005-07-18 04:07:50 EDT
3.1

- create new workspace
- binary-import org.junit
- exit
- zip workspace
- delete workspace
- unzip workspace
- start eclipse
- open-type TestCase
-> "The file has been changed on the filesystem. Do you want to load the
changes?" dialog; from now on this shows up everytime the class file editor opens

Filing against JDT/Text to start with, because the CU editor works fine.
Comment 1 Dani Megert CLA 2005-07-18 10:16:29 EDT
We handle this for text and Java source files but not for class files in JARs:
we need to refresh the JAR itself.

Note that many other functions do not work if you simply unzip a workspace
without refreshing it, e.g. search in text or source files is not possible until
you refresh the corresponding file(s).
Comment 2 Eclipse Genie CLA 2019-12-24 06:26:17 EST
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.

If you have further information on the current state of the bug, please add it. 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.
Comment 3 Eclipse Genie CLA 2021-12-17 17:37:09 EST
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.

If you have further information on the current state of the bug, please add it. 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.
Comment 4 Eclipse Genie CLA 2023-12-08 18:59:10 EST
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.

If you have further information on the current state of the bug, please add it. 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.