How to split/divide exiting RTC component into new ones?
Does RTC scm has the functionality somewhere to allow user to split/merge exiting components into new ones?
Say I have one component A with three top folders f1, f2, f3 and I want to created three new components and each will just hold one of them and maintain the original history in A. I don't see a direct way to do it except the Replace with command. Is it possible to just create anew component and move a whole folder from another component into it? |
Accepted answer
Geoffrey Clemm (30.1k●3●30●35)
| answered Feb 09 '10, 11:53 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Yes, you can do the refactoring after the import.
The history will not actually get moved to the new component, but a backlink to the imported history will be stored with the versionable in the new component. And the refactoring works on any files and directories, not just Java source code. Cheers, Geoff ghu wrote: gmclemmwrote: Ralph Schoon selected this answer as the correct answer
|
20 other answers
https://jazz.net/help-dev/clm/index.jsp?topic=%2Fcom.ibm.team.scm.doc%2Ftopics%2Ft_scm_eclipse_mv_project.html
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Aug 30 '11, 7:10 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Jay,
I added a comment to that work item ... see if that answers your question (let's continue the discussion in that work item). Cheers, Geoff On 8/28/2011 2:23 PM, jaybrubin wrote: Geoff is this RFE not a valid process usuage: |
Geoff is this RFE not a valid process usuage:
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=175331 Work Item = 175331 "can their be a simple way we can clone a clone repository workspace / component that will have no linkages to the source component we want to clone. happy to use snapshots or flow targets; but don't want connected baselines after clone. command line is fine too." is this eclipse move folder something to investigate? |
Hi
I used "Move into Repository" to move three root folders in one component to three other components. Basically I split one component with 68K files and folders into four components, in fear of performance issues. Now there are two components, Client and Server still have 20~30K files and folders. I notice Deliver and especially Accept take a few minutes, e.g. after create a new snapshot in workspace. My questions is: does split help in performance or still constrained by the original 68K files in the original component, due to maybe a link back to the original component. Shall I delete everything and re-import the files? Do you have 30K files in one component? Thanks Jirong |
Geoffrey Clemm (30.1k●3●30●35)
| answered Aug 02 '11, 8:46 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Yes, if you have several (non-root) folders that you want to move to
another component, first moving them all to some dummy root folder in the source component would require fewer operations (you just have to remember where you wanted each of those folders to end up in the destination component). WRT creating a baseline in the source component, it is very easy in RTC to back-up to an earlier configuration of a component ... just discard/suspend the change sets involved in the move ... but it never hurts to create a baseline as well. Cheers, Geoff On 8/2/2011 4:23 AM, dmaaren wrote: Hello Geoff, |
Hello Geoff,
This discussion was very helpfull to me to move files between components. I think a little improvement is possible regarding your workaround. What about creating a dummy root folder in the source component. Then you can move all the files you want to transfer in this dummy root folder. After the "Move in repository" action (of this dummy root folder), you don't need to bother anymore about the source component. Also I think it's wise to make a pre-move baseline of the source component, before starting the whole operation. If something goes wrong, you can always revert to this baseline. Greetings, Dick van Maaren. Please see the correction I posted to my earlier posting. To summarize gmclemmwrote: |
Geoffrey Clemm (30.1k●3●30●35)
| answered Feb 20 '10, 1:53 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Since you posted the request against RTC, they assumed you were
referring to the "move in repository" operation (which is an RTC operation), as opposed to the "move" operation (which is an Eclipse operation, that is enhanced by RTC, but whose core semantics are defined by Eclipse, not RTC). And work item 21637 does ask for the functionality you describe in 106422, so marking it as a duplicate was correct (as long as this is interpreted as asking for enhanced functionality from the "move in repository" operation). Cheers, Geoff ghu wrote: gmclemmwrote: |
Geoffrey Clemm (30.1k●3●30●35)
| answered Feb 20 '10, 1:53 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Please see the correction I posted to my earlier posting. To summarize
the correction, backlinks are only created by the "move in repository" operation, not the Eclipse "move" operation. Also, note that the way the GUI displays these backlinks is to have a "break" in the history line that is drawn to the left in the "history" view on a file. That "break" represents the backlink to the earlier history of that file in another component. Cheers, Geoff ghu wrote: gmclemmwrote: |
Geoffrey Clemm (30.1k●3●30●35)
| answered Feb 20 '10, 1:38 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
A correction/clarification to one of the points I made below.
In particular, I said: you can use the plain old "Move" command Although that statement is true, it is misleading because the plain old "Move" command when used to move a file/directory to another component does *not* create the back-pointer to the previous history. I've just added a comment to work item 56504, asking that it do so. So the only way I know of to move files/folders across components while creating history back-pointers is to use the "move in repository" operation ... and that operation appears currently to only be supported on root folders within a component (i.e. folders that are logically immediate children of the logical component root folder). So until work item 56504 is implemented, the only workaround I can think of to achieve this cross-component move of selected files/folders while creating history back-pointers, is: - use "move in repository" to move the tree containing the file/folders you wanted to move into the destination component. This will create the tree as a new root folder in the destination component. - use regular "move" to move the file/folders where you really wanted them to move within the destination component. - use "delete in repository" to delete the tree in the destination component. - in the source component, discard the "move in repository" change set (this will cause that tree to reappear). - in the source component, delete the files/folders that you moved to the destination component. If anyone knows of a simpler workaround, please post it. Cheers, Geoff Geoffrey Clemm wrote: Comments below: |
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.