RTC Eclipse client: no actual difference - why there's a change in the change-set ?
Reproduced in 6.0.6.1.
The following was found while running the scenario through client API, but I managed to reproduce it using RTC Eclipse client UI:
I have a file named file1.txt located in folder A. I have eclipse project for the component containing folder A. In this component there's another folder B. I move file1.txt to folder B while using the Eclipse project (drag and drop the file from A to B). I check-in the change into a change-set. Now I move file1.txt back into folder A. I check-in again the change into the same change-set. I expect to have an empty change-set, but no - file1.txt is still there, without the move label, but it is still there. I double click on it and I get the indication saying there are no differences.
Is this an expected behavior or a defect ?
Accepted answer
This is working as designed. The file now has 2 different states checked into that change set. For example, right-click on the file in the change set, and select "Show History", now in the History view, use the view menu (down arrow at top right) and select "Show Check-in History". Now with the change set selected in the History view, you will notice that there are 2 states (version IDs).
The same situation can happen with content changes instead of moves. For example, open the file, and append 'a' to the end of the file and check that into a change set. Now remove 'a' from the file and then check that into the change set again. Opening the file in the compare editor will reveal no 'content' changes, even though there is a new state/version for the file.
If you don't want this file to appear in the change set, use the "Undo" action.