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

Re: refactor doesn't trigger svn move

From: Mark Phippard <markp_at_softlanding.com>
Date: 2005-12-02 18:11:46 CET

Marco Schulze <Marco@NightLabs.de> wrote on 12/02/2005 12:06:39 PM:

> But this seems not to be the case :-( I just renamed a java class and it

> is displayed as new file (with the little "+" symbol) instead of being
> moved. Did I do anything wrong?
> It would be absolutely great, if subclipse would hook into the
> refactoring and do a subversion-move instead of deleting and re-adding
> the files. Thank you very much in advance for considering my feature
> request!

Subclipse does do an svn move. If you look in the Console view you can
see the commands we execute.

In Subversion a move is implemented as a copy (add with history) + delete.
 You see a + decorator because the new moved file is now a scheduled Add
to the repository. When you commit, you will want to perform the commit
from a common parent and commit the delete and add together. After you
commit, a Show in Resource History on the moved file will show you the
history of the file prior to the move. That is essentially, all this
feature in Subversion gives you.


Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
Received on Sat Dec 3 04:11:46 2005

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.