camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject [BEWARE] - Moving classes - Keep SVN revision details
Date Thu, 08 Sep 2011 06:16:50 GMT
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.


-- 
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

Mime
View raw message