Reinhard Poetz wrote:
> Gabor Nagypal wrote:
>
>> Hi,
>>
>> I gave a try to subclipse+subversion recently and I noticed that if
>> you do refactoring in a Java project (e.g. Refactor/Rename), instead
>> of a subversion move command an add and a remove command are
>> scheduled. As a net effect, after the commit I loose all of the
>> history information on the renamed file. Is there some possibility to
>> change this behaviour?
>>
>> In my opinion onw of the best things that subversion can provide is
>> the support for file-renaming, this makes it possible to do
>> refactoring and version control at the same time, a feature which was
>> not possible with CVS.
>>
> See http://subclipse.tigris.org/issues/show_bug.cgi?id=108
> In short: It's not a problem with losing the history but a problem
> with showing the complete history in Subclipse.
>
> BTW, a move in subclipse is equivalent to copy and delete
> (http://svnbook.red-bean.com/svnbook/re18.html)
>
You can easily verify this. If you rename a class and then go to the svn
command line client and type *svn status*, you'll see the old Java file
marked for delete (D) and the new one marked for add (A) with a "+" next
to it to denote that it is carrying its history with it.
I find I use the svn status command a lot - it's a very nice quick
reference for what's changed, and extremely easy on the eye.
Cheers,
Dan
Received on Tue Aug 3 09:58:39 2004