Community
Participate
Working Groups
Here is the scenario. I said Replace With->Another Branch or Version..., and then chose a specific branch (Call it branch_3_4). In the middle of replacing, I got an error message complaining about a file it tried to write and couldn't. That's fine, removed the local file. Chose Replace With->Latest From Branch branch_3_4 this time and it seemed to finish with no errors. However, I noticed that one of the files I was working on in what I now thought was the branch was actually a file from HEAD!!! I then said Replace With->Another Branch or Version... and chose branch_3_4, and this time it seems to be the right version. The problem seems to be that if an error occurs on replace with, eclipse winds up in an inconsistent state. This bug could be disastrous, as we need to patch a release and if I didn't notice the problem I could have gotten files from HEAD out into production unintentionally!!! Please advise. Regards
The implementation of the replace with is not done in a two stage commit. To undo, we would have to perform another replace. I agree that it should be *much* more obvious that your project is in an inconsistent state when the operation fails.
Post 3.0
*** This bug has been marked as a duplicate of 42509 ***
