![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: Changing the project heirarchy under 6.3 Topic Summary: Created On: 6-Aug-2003 14:34 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi,
We currently have one big project with about 20 directories. I would like to make some of the directories into subprojects, and other directories into sub-projects of the sub-projects. For example, if currently project P has subdirectories A, B, and C, I would like to change this so that Project P has sub-projects A and B, and subdiretory C is now a sub-project of B. Of course, the entire revision history of all of the controlled objects should be maintained. Any hints, clues, ideas, solutions or pointers would be greatly appreciated! Thanks, Rony |
|
![]() |
|
![]() |
|
Your solution is to create your own working project and create your subprojects with the command lime from the work-area: ccm create -t project -root directory_of_new_project
see ccm create help for more info example: # create your task and set it by default $ setenv CCM_ADDR with rigth value $ cd ~/ccm_wa/mybase/theproject~myversion/theproject # create the project with same name as directory $ ccm create -t project -root mysubdir -v myversion # to remove the directory $ ccm unuse mysubdir # and replace by project $ ccm use mysubdir~myversion .......... When all is done, check if you want relative project (work area properties) and check if reconfigure properties are ok (propagate properties from top project) And check-in your task. The task will reference all your work and the build manager can also use your project tree (CI to prep or share and prep) to create the new prep subproject . If the build maanger to this work directly on a prep project work-area (without any reconfigure), it can create directly the project with prep state. After these all operations, users must better delete their own project and check-out another one from prep or a new created baseline. Regards, ------------------------- Pierre Guillet |
|
![]() |
|
![]() |
|
Wow - that was quick - thanks!
In the meanwhile, I found reference to a command that might also do the trick - "ccm move". Are these solutions equivalent? If not, what are the differences? Cheers, Rony |
|
![]() |
|
![]() |
|
Hi,
You can use ccm move to rename an object (directory, file or project) or to move it in the same project or another project. You can use it to transfer your files/dir in another created project but you will create another instance of the parent directory, another version of the current instance and cut the changes made to the native directories. Ex: ccm_wa/mybase/proj1~myversion/proj1/file1 ...../mydir/file2 you are using mydir~1:dir:1 (directory named mydir, version 1, instance 1) which references the file named file2. You want to transfer mydir contents into mydir project (same name because the parent directory of the project takes the same name). You create the project $ ccm create -t project -n mydir -v myversion. This command will create the project parent directory mydir ~1:dir:2. You move the files (i.e. file2) into the new created project $ cd ~/ccm_wa/mybase/proj1~myversion/proj1/file1/mydir $ ccm move * ~/ccm_wa/mybase/mydir ~myversion/mydir The instance 2 of mydir will reference file2 and version of instance 1 will be incremented (move do an unuse in instance 1 and an use/add object on instance1. In the meantime if another user adds a new file to mydir (instance1), the reconfigure on your new project don't fetch this new file into mydir instance 2 because it's a new instance. The create project with -root option will use the SAME instance of dir and will fetch this new file. QED Better to use -root option. Regards, ------------------------- Pierre Guillet |
|
![]() |
Telelogic SYNERGY
» SYNERGY/CM
»
Changing the project heirarchy under 6.3
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.