SVN Scenario: How to do this in Jazz SCM?
My team has been using SVN and I am studying the possibility to migrate to Jazz SCM.
The whole source code is in the following structure :
C:\a
C:\a\b
C:\a\b\c
C:\a...
C:\a have various contents, among them, b is a Java Eclipse project which requires to sit inside a to work, and c is an independent Java Eclipse project but required by b
In SVN repository, I use the following structure:
/trunk/a
/trunk/a/b --> empty dir with svn:external to /trunk/b
/trunk/b
/trunk/b/c --> empty dir with svn:external to /trunk/c
/trunk/c
this way, I simply :
- check out /trunk/a to C:\a, then in Eclipse I import C:\a\b as a project to work (since b requires to sit inside a)
- check out /trunk/c on anywhere, and import it as project in Eclipse to work independently
to create a build, all I have to do is svn-export C:\a and package it.
All the RTC documentations I found seems to assume every components are independent of each other and no nested relationship. When trying to migrate to Jazz SCM, I have no idea how to deal with such nested structures, can anyone assist on this?
Accepted answer
The setup I would try for this would be something like
Component
--a
----b
------.project
--c
----.project
It appears from your description that b must be a child of a in both the
repository and on disk. However, it also appears that c is within b in
the repository for some reason. I am hoping this isn't a restriction
since it is a bit tricky to deal with next Eclipse projects.
To load this content, I would use the "Load folder" option in the RTC
load wizard and on the second page, I would select a and c (the
top-level folders) and then, expand the Advanced Options section and
select the option to find and load Eclipse projects. If my sandbox (or
Eclipse workspace) was C:\sandbox, this would result in the following
structure locally
C:\sandbox
--a
----b
--c
where b and c would be projects in Eclipse. Does this meet your
requirements?
Michael