: : 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? (i'm not saying i think we should try to revert and do it again with "svn copy" I'm just wondering if there's something i'm missing about this appraoch that we should keep in mind the next time we want to refactor some classes) -Hoss
