svn - Subversion refactor trunk and still be able to merge changes to old branches -
what best practices in situation refactor trunk in svn cannot apply refactor older branches, yet still need able svn merge bugfixes trunk branches?
to ask question more (if helps - if can answer above, feel free ignore):
we want move maven going forward, still need maintain old releases - cannot touched except customer sanctioned changes , bugfixes.
so, need refactor our folder structures around in trunk per maven - src/main/java, src/main/webapp etc (its wtp project - src, webcontent instead of above).
but going forward, still need able svn merge older branches still in old folder structure.
is possible? best practices?
i know can apply changes trunk, , apply changes branch manually, result in lot of pain developers want avoid.
apologies if answered or obvious (i have thought be, feel i'm asking obvious question!)
thanks in advance, justin
if move things around can still use svn merge, not straight on. svn merge not track moved files.
at lowest level can merge on per file basis, if move complete subdirectories can merge each "untouched" subdirectories @ once. there more steps involved , need track manually things has been moved.
Comments
Post a Comment