It's all about the answers!

Ask a question

Importing from SVN - concepts

R jose (2158) | asked Mar 13 '13, 9:20 p.m.
edited Mar 13 '13, 10:00 p.m.

I am trying to import several projects from SVN to RTC 4.0. I am trying to clarify some of the concepts. Please help...

We have several  web modules (eclipse projects) taking to single "data access" project (java module and also an eclipse project). There is also a db project where we have the build scripts (also an eclipse project). While importing to Jazz do I need to create a component for each eclipse project inside  a single stream (say development stream). There will be mutiple teams working on the same projects. So, I am thinking there'll be 5 'dev' streams? And, then then there will be 1 green dev stream which has everybody's changes consolidated.

From the green stream there will be an integration stream where we will have CI set up. Do I need to setup a flow target for this?

Also, instead of loading directly from jazz , I have loading the projects to my workspace and then checking them into jazz but that I am unable to share the components with other streams. Any idea why? The error I am getting is "Sharing projects encountered a problem - An Internal error occured". Looks like I don't have permission, is that right?

Accepted answer

permanent link
Lauren Hayward Schaefer (3.3k11727) | answered Mar 14 '13, 6:59 a.m.

If you haven't seen, you may find it very helpful.  It explains how the concepts from SVN translate to RTC.

You can have multiple eclipse projects in one component. explains multi-stream development.

Can you explain which action you are doing when you get the error message?  Does the error message have any more details?
R jose selected this answer as the correct answer

One other answer

permanent link
Tim Mok (6.6k38) | answered Mar 14 '13, 11:02 a.m.
How you want to set up your projects and components is up to you. You'll want to see how each team is loading the projects and decide if they want their own components. For the projects shared among the teams, it'll make sense to put it in a component common for all the teams. Then each team can load that component without having to load other team's resources. If all the teams are loading the same resources then one component is probably enough.

If you care about history, you'll probably want to use the SVN importer. See

Your answer

Register or to post 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.