How get (erroneous) baselines created by the SVN import wizard?
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. Several issues occur when importing that repository into SCM:
|
One answer
The SVN importer was written expecting the repository layout of
trunk folder1 tags tag1 folder1 tag2 folder1 folder2 branch branch1 folder1 branch2 folder1 folder2 Your structure differs from that so the importer is being thrown off. The import should work as expected for branches but will not create the baselines you would like for your tags. This difference in structure is also contributing to what you are seeing in point 3. Suffice it to say that the importer relies a bit too heavily on the assumption that the above pattern is used to organize the repository. Comments
Steffen Weik
commented Dec 19 '13, 11:11 a.m.
I understand that the baselines for the tags on the branches are not created correctly. We will have to decide whether it is worth the effort to migrate those tags / branches manually or not.
|
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
I could provide a small svndump but do not know how to attach a file here, any hints about that?