camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Schneider <>
Subject Re: [BEWARE] - Moving classes - Keep SVN revision details
Date Thu, 08 Sep 2011 06:36:35 GMT
I also wondered why this happened as I used a eclipse refactor command 
like before. I guess it happened as my eclipse workspace was not 
connected to svn at the time.
Normally I try to move classes in svn.


Am 08.09.2011 08:16, schrieb Claus Ibsen:
> Hi
> When you refactor the code such as moving classes to new packages,
> etc. Then try to make sure to use svn mv so so we keep the svn
> revisions of this class. If you do a delete and add instead, we loose
> all that details.
> This is important to keep as it helps resolving issues as you can
> compare with past versions, and also on a line by line bases see
> who/when/commit logs what has been changed.
> For example the class AsyncProcessorTypeConverter was moved in the
> last commit. But the commit was a delete + add, which means all the
> previous commit logs of that class is gone.

Christian Schneider

Open Source Architect

View raw message