[Subclipse-users] Two consecutive move operations reset resource history

Hello!

I'm a bit confused by Subclipse's behavior when doing two consecutive
rename/move operations for a single file in Eclipse. For example, when
renaming first.txt to second.txt and immediately after that to third.txt
without a commit in between, Subclipse performs the following
operations:

move C:/test/first.txt C:/test/second.txt
    A C:/test/second.txt
    D C:/test/first.txt
add -N C:\test\third.txt
    A C:/test/third.txt
delete --force C:/test/second.txt
    D C:/test/second.txt

As a result of the latter explicit add and delete operations, the
resource history of third.txt is reset i.e. it shows nothing about
first.txt or second.txt. If, however, a commit was made after renaming
first.txt to second.txt, the resource history would then be ok all the
way up to third.txt.

In my opinion, Subclipse should disallow the second rename operation in
eclipse, instructing the user to do a commit first.

I couldn't find this issue in the Subclipse issue tracker so I decided
to give it a go and ask your opinions about it.

With best regards,
Sampsa Toivanen
HiQ Softplan Ltd., http://www.hiq.fi

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Mar 21 11:15:20 2006