Changesets that have two changes on same file

Hello,

We faced with a problem on our build engines and we had to look at the
changesets in depth and we detect two changesets that have two changes
on same file.

Hope screenshots tells more than words:

Case1:

http://tuanaweb.com/img/addAndDelete.JPG

In fact I can't reproduce this!! First I thougt it can be created with
an old version but it's creation date is after our v.3.0.1 update..


Case2:

http://tuanaweb.com/img/deleteAndAdd.JPG

Well this is the screenshot of reproduced case.

I think this must be bug, just think you delete a file with a mistake
and than restore it from eclipse. Then you will deliver a change for
that file while it is not changed. Also you will see is as two
different files in your component history.

Well, if it is something done intentionally, please somebody tell me
the process order when accepting this changes. Cause for both changes
RTC keeps the file in local workspace.

This problem affects our custom build engine tool which uses
RTC-Client-plainJavaLib-3.0.1 and RTC-BuildSystem-Toolkit-Win-3.0.1
libraries. It accepts changesets, loads only accepted files file by
file and organizes the local files(Detects old-new paths and
changekind for a change and adds, deletes or modifies file) For these
two changesets it's behavior is different than RTC. RTC always keep
the added - modified file but our tool does not keep the file for all
cases. When the same file modified, it can't find the old file in
local workspace and produce an error then forces a complete load of
the component with final config.

Thanks in advance!

I believe what happened in case1 is that it actually was the same as
case2, i.e. a file was deleted, and then a new file with that same name
was created. But you (and your scripts) are being confused because when
the Change Explorer encounters this case when the deletion and addition
are in different change sets, it appears to show the deletion before the
addition (even though the changes really occurred in the opposite order).

To determine whether this is what is happening in your case, look at the
history of the component and see if the deletion comes before the
addition. It is likely that is what happened, because you indicate that
the file still exists.

Cheers,
Geoff