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

Bug 266339

Summary: Replace with Latest from HEAD keeps uncommitted changes
Product: [Eclipse Project] Platform Reporter: Tomasz Zarna <tomasz.zarna>
Component: CVSAssignee: platform-cvs-inbox <platform-cvs-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3    
Version: 3.4   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description Tomasz Zarna CLA 2009-02-26 11:27:49 EST
First seen on I20090217-2200, but reproducible on stable 3.4 as well.

Steps:
1. Edit a shared file, save
2. Sync the project, double click in the Sync view to open Compare Editor
3. Remove the file in Package Explorer, the Compare Editor becomes "half-empty", outgoing change in the Sync View changes to outgoing deletion, fine.
4. Right click on the project, select Replace > Latest from HEAD, confirm overwriting uncommitted changes*
5. Open the file
=> the changes made in 1. are still there and the project claims to be sync'ed with HEAD, no ">" indicator

* the uncommitted changes, made in 1. will be kept when you choose to Restore from Repository/Local History but I guess this is a feature not a bug given the fact that sync info is fine
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:06:43 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.

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.
Comment 2 Eclipse Genie CLA 2022-01-23 05:56:40 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. 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.