Chris Hostetter wrote:
:
: 1. Using eclipse, refactor common classes and *move* them to the new
: 3. Add a @deprecated new class in the place of any moved class. The new
: class will have the same name and extend the old class. They will not
: have version history. These files will be deleted when we have a
I'm curious, why the specific choice to "svn move" the files and then add
new ones in the old locations? ... wouldn't "svn copy"ing the files
and then trimming down the old paths have left a better audit log of what
happened?
The real command was "eclipse (with subclipse) drag, then drop" ;) This
gets converted to an svn move. There must be a subclipse copy/paste...
I did not think about (know about) svn copy - you are right, that would
be better to have the history on both files. If we have to move
anything else, we should use that approach.
ryan
