How to import a SVN repository, containing components renamed in history?
I have a SVN repository that is structured like the one in the following example:
component branches branch1 branch2 tags branch1 tag1.1 tag1.2 branch2 tag2.1 tag_on_trunk trunk other_component ... Imagine that each of the leaf folders above contains several eclipse projects. Also imagine that the component got renamed or moved several times during its history. The following issues occur in that case:
|
Accepted answer
Steffen,
Unfortunately, the SVN importer doesn't have automated support for the types of copies you described. Here is a general set of steps that might work for you: 1) Import the changes before the copy into the target component 2) Discard the last change set containing the delete from the target component 3) Import the changes after the copy into the same component a) Ensure the "reconcile" option is checked b) When prompted to import a branch or to import starting at a particular revision, you should click No Do those steps work for you? Steffen Weik selected this answer as the correct answer
Comments
Steffen Weik
commented Dec 19 '13, 10:56 a.m.
Actually importing using these steps at least solves problems 3 and 4. Thanks for the advice!
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
An update: issues 1 to 3 even occur without renaming the component.
I deleted those issues here and moved them to a separate question.
I could provide a small svndump but do not know how to attach a file here, any hints about that?