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?