[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] Move/rename integration

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-03-08 21:40:14 CET

Thomas Timbul <ttimbul@gmail.com> wrote on 03/08/2006 03:32:23 PM:

> One of the reasons I moved from CVS to SVN was because of rename
> support. This is fine when used outside of eclipse, but with subclipse
> there seems to be little (if any) integration with the platform for
> detecting when a file has been renamed or moved.
>
> Instead, any rename or move operation is detected as the removal of the
> original file and the addition of the file with the new name, thus
> defying the purpose of supporting rename in the first place...
>
> Maybe somebody can advise? (You never know, there could be a silly
> workaround, like... don't use JDT, but the 'resource navigator' to do
> your refactoring)

When you do a move or a rename, Subclipse executes the svn move
command/API. Open the Eclipse Console and you can see what it does.

Internally in Subversion, the move command does an Add (copy) followed by
a Delete.

This is a pretty common thing that confuses people. The main benefit you
get from doing a move in Subversion is that after you commit, the history
of the file will trace back past the copy to the previous version.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Wed Mar 8 21:40:52 2006

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.