Welcome to the Jazz Community Forum
SVN import from branch without project folder
Hi there,
In my project I have to migrate from a SVN repository where there is onlyone Eclipse project per branch.
So in the SVN dump the structure is:
So when I import with the SVN Importer I end up with
either a structure like
which has no folder for the Eclipse project
or I get a structure like
where the name of the Eclipse project is 'trunk' or the name of the branch.
Has anyone an idea how to map such a structure into a reasonable Eclipse project, when doing the SVN import?
Thanks.
Robert Studera
In my project I have to migrate from a SVN repository where there is only
So in the SVN dump the structure is:
project
branches
BRANCH1
src
lib
...
BRANCH2
...
tags
trunk
src
lib
...
So when I import with the SVN Importer I end up with
either a structure like
COMPONENT
src
lib
...
which has no folder for the Eclipse project
or I get a structure like
COMPONENT
trunk
src
lib
...
where the name of the Eclipse project is 'trunk' or the name of the branch.
Has anyone an idea how to map such a structure into a reasonable Eclipse project, when doing the SVN import?
Thanks.
Robert Studera
2 answers
The importer doesn't support renaming of folders during import. However,
you can load a component root folder as a project (just as you can load
trunk as a project using SVN) so the first structure you mentioned would
be the structure you want (i.e. the Component itself acts as the Eclipse
project).
Michael
studera wrote:
you can load a component root folder as a project (just as you can load
trunk as a project using SVN) so the first structure you mentioned would
be the structure you want (i.e. the Component itself acts as the Eclipse
project).
Michael
studera wrote:
Hi there,
In my project I have to migrate from a SVN repository where there is
only one Eclipse project per branch.
So in the SVN dump the structure is:
project
branches
BRANCH1
src
lib
...
BRANCH2
...
tags
trunk
src
lib
...
So when I import with the SVN Importer I end up with
either a structure like
COMPONENT
src
lib
...
which has no folder for the Eclipse project
or I get a structure like
COMPONENT
trunk
src
lib
...
where the name of the Eclipse project is 'trunk' or the name of the
branch.
Has anyone an idea how to map such a structure into a reasonable
Eclipse project, when doing the SVN import?
Thanks.
Robert Studera
Thank you, Michael!
This would be a solution for the initial migration. In the long run we might want to have more than one eclipse project in one component, But that will be a major reorganisation anyway
Robert.
This would be a solution for the initial migration. In the long run we might want to have more than one eclipse project in one component, But that will be a major reorganisation anyway
Robert.
The importer doesn't support renaming of folders during import. However,
you can load a component root folder as a project (just as you can load
trunk as a project using SVN) so the first structure you mentioned would
be the structure you want (i.e. the Component itself acts as the Eclipse
project).
Michael