SVN import with unusual structure of Eclipse projects
The help and wiki ( https://jazz.net/wiki/bin/view/Main/ ) describes how to do this for a standard configuration in SVN, where the SVN looks like:
trunk An unwritten assumption in the above I think, is that the "folderX", "folderY", "folderZ" are the individual (Eclipse) projects. This is not how our SVN is laid out. We have an SVN structure where each Eclipse project folder has (in SVN) its own trunk, tags, and branches. We routinely tag individual projects to mark integration levels. It looks like folderX Can this structure be imported into RTC? Would the right approach be to create "components": 1 for each Eclipse project? (That way, it seems, we could emulate creating a "baseline" for each Tag). -Marshall Schor |
9 answers
Yes, you would need to import this by mapping the project folder (e.g. trunk) to the component root folder. |
Geoffrey Clemm (30.1k●3●30●35)
| answered May 03 '11, 11:01 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Yes, you could create component for each project, but that would
probably produce an excessively large number of components. Unless you count on the ability to select an arbitrary tag for each project to compose your configuration, the stream for a .psf file approach is simpler. Cheers, Geoff On 5/3/2011 9:53 AM, marshallschor wrote: The help and wiki ( https://jazz.net/wiki/bin/view/Main/ ) describes |
Hmmm. Saying this can be done, seems to conflict with the help I found for version 3.0, which said:
Note: Repository organizations where the trunk folder itself maps to an Eclipse project are uncommon and are not supported by the importer: trunk We're planning to work around this by making a new node in our SVN and "copying" the data, to conform to the style which is supported by the RTC import capability. -Marshall
Yes, you would need to import this by mapping the project folder (e.g. trunk) to the component root folder. |
Hmmm. Saying this can be done, seems to conflict with the help I found for version 3.0, which said: What doc was this? It wasn't supported initially (1.0) but should certainly work now. Let me know the documentation you were referring to so I can make sure it gets updated. P.S. I'm pretty sure your work around would lose the history for the items being imported. |
I believe the layout Marshall describes, we'll call this the project-trunk layout (the eclipse .project is immediately /trunk) is much more common and conceptually cleaner (especially for java projects built with maven - where ingesting artifacts from different projects is trivial) than the projects-as-branch-siblings layout described as 'most common' in the online help and given as an example in the jazz.net wiki.
I believe it's cleaner as a project is something that is built, versioned, tagged and released as a unit. It seems odd to me to checkout multiple projects just to build one, or tag multiple projects at a go. From the svn book:
I'm very new to svn, but I'm having a hard time seeing a situation where I'd want more than one eclipse project per component, or have more than component per project. Thoughts? |
Hmmm. Saying this can be done, seems to conflict with the help I found for version 3.0, which said: What doc was this? It wasn't supported initially (1.0) but should certainly work now. Let me know the documentation you were referring to so I can make sure it gets updated. P.S. I'm pretty sure your work around would lose the history for the items being imported. The doc is here: http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0/index.jsp?topic=/com.ibm.team.scm.svn.doc/topics/c_svn.html scroll down to the first "Note:" -Marshall |
I have entered https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/164821 to request that the note be removed since that scenario is now supported.
|
There's still maybe an issue.
Contemplate 100's of Eclipse projects, each having the structure: proj-name Is this the process that would be needed: 1) select a particular proj-name/trunk in the import 2) import into a component (resulting in the component having a new top-level folder, called "trunk" 3) do some action to rename the component top level folder "trunk" back to proj-name repeat the above for the 100's of projects, each individually. I have entered https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/164821 to request that the note be removed since that scenario is now supported. |
I think it would be worthwhile to capture this in an enhancement request against RTC Source Control.
|
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.