Community
Participate
Working Groups
3.5M7 Steps: 1. Open Compare Editor for two local files 2. Edit file on the left (do not save) 3. Open the same file outside Eclipse, edit it and save 4. Switch back to Eclipse 5. Save => 3.4, a dialog will pop out to inform that save cannot be made because the file is out of sync. At the same time, dirty indicator is cleaned giving a false impression that changes made in Eclipse are saved. Any subsequent changes made in Compare Editor will not succeed (changes will be lost) until the file doesn't get refreshed. => 3.5, save silently overwrites the content changed on the file system. I believe both situations are bad, in the first we lose Eclipse changes, in the second we lose these made outside Eclipse. What we are able to observe in 3.5 may be another (bug 275153) regression introduced when replacing ResourceCompareEditorInput with SaveablesCompareEditorInput (bug 193324). imo this issue can be considered as a faulty feature rather than a regression.
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.
