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

SPAM[RBL] Re: Slow "move" discourages refactoring.

From: Mike Mason <mgm_at_thoughtworks.net>
Date: 2003-11-27 17:37:22 CET

Leeuw van der, Tim wrote:

>When doing software-refactorings in f.e. Eclipse, I tell the IDE to
>move/rename a directory. The IDE communicates to the version-control-tool
>(in case, SVN) that the directory needs to be renamed. It then modifies all
>java-files where needed to change the package-declarations and imports.
>This of course happens as a WC operation.
>I think that most software-refactorings happen as WC operations, because you
>want to try something, perhaps revert, try something else, change all source
>files and build files to reflect the new new layout and naming, make sure it
>builds, etc... And then commit.
>Looking at how I do refactorings, I don't think it's realistic to expect
>URL-to-URL moves when I'm refactoring my code but only moves in the WC. It's
>the way my tools work.

Aha, then you're right that doing it on the working copy is the correct
thing to do. How does Eclipse do a move? IntelliJ will ask its VCS
plugin to move each file in turn, which could cause problems if you do
it on a big directory. Calling out to Subversion once for each file
might well be the slow things down.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 27 17:38:09 2003

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

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