Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 21997

Summary: Replace with latest did not automatically refresh editor
Product: [Eclipse Project] Platform Reporter: Philipe Mulet <philippe_mulet>
Component: TextAssignee: Platform-Text-Inbox <platform-text-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: major    
Priority: P3    
Version: 2.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows 2000   
Whiteboard:

Description Philipe Mulet CLA 2002-07-29 06:35:09 EDT 
Build R2.0

Took a compilation unit, edited it, saved the file.
Then decided the change was not good, so undid my change (using undo), and 
finally did choose to replace with latest from repository.

When doing so, it did prompt me for saving the unit (said no). It then did 
inform me that I was about to lose some local changes (said yes).

After replacement did occur, the editor was still showing me the last edited 
content. 

Had to type in some more characters to see a dialog saying it had changed on 
the filesystem and prompting for reloading.

This last step is bogus, replacement should have triggered editor refresh since 
I had made it clear I wanted to get rid of my local changes.
Comment 1 Kai-Uwe Maetzel CLA 2002-09-11 14:47:32 EDT 
If the editor is dirty, replace with latest does not change what the editor 
shows. From the editor's perspective, there is no difference between a team 
action and something else happening on the file system. 

There needs to be a general concept in the workbench. This can be either a way 
to reload an editor externally or a mechanisms that allows receivers of 
resource change events to determine what class of action caused the change. As 
we already have something similar (move flag on resource deltas) I think the 
second solution would be better.
Comment 2 Dani Megert CLA 2005-06-16 05:58:46 EDT 

*** This bug has been marked as a duplicate of 96336 ***