Hello, I have searched before starting this topic, so I apologize if someone else asked the same question. When I copy a module (copy and normal paste) I see the version of the last baseline of the source module in the title bar of the new module, moreover the source module history is preserved. In the example of the attached jpg, I can create a new baseline starting from version 2.0 without having the previous baseline versions.
I would like the new module to start from version 0.0 with a cleaned history, any ideas?.
Thanks in advance, Dario
Dario_Imparato - Wed Apr 05 06:03:02 EDT 2017 |
Re: Copy Module Without Baseline and History Info Hello, If there is no need to keep the old baseline, then you can simply "copy" baseline. File > Baseline > Copy then select baseline you want to copy. This way you can start the baseline from number 0.0.
|
Re: Copy Module Without Baseline and History Info knobutan - Mon Apr 10 01:07:26 EDT 2017 Hello, If there is no need to keep the old baseline, then you can simply "copy" baseline. File > Baseline > Copy then select baseline you want to copy. This way you can start the baseline from number 0.0.
Except with that method the Object Identifiers are not kept. If that is not important, then the copy baseline method works.
Otherwise see the partition method in https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014846666 |
Re: Copy Module Without Baseline and History Info Hello, thanks for your answers. I have no need to keep the Object Identifiers, but I should copy the current version of the module, not the baseline. You could say "ok create a baseline of the current"...yes, in some situations it could be possible, but in others it couldn't...
I would like to use the "directory copy" functionality with copied modules at 0.0 version. The DOORS copy works very well with links, if I have in a Directory "D" two modules A and B with links A->B in module A_Link_Module in the same dir (D), and I copy D, Doors copies also the links from newA -> new B in a new link module "newA_Link_Module". I would like to preserve this behaviour, cleaning the wrong informations on the version (and possibly removing history).
Thanks in advance, Dario
|
Re: Copy Module Without Baseline and History Info Dario_Imparato - Mon Apr 10 04:27:03 EDT 2017 Hello, thanks for your answers. I have no need to keep the Object Identifiers, but I should copy the current version of the module, not the baseline. You could say "ok create a baseline of the current"...yes, in some situations it could be possible, but in others it couldn't...
I would like to use the "directory copy" functionality with copied modules at 0.0 version. The DOORS copy works very well with links, if I have in a Directory "D" two modules A and B with links A->B in module A_Link_Module in the same dir (D), and I copy D, Doors copies also the links from newA -> new B in a new link module "newA_Link_Module". I would like to preserve this behaviour, cleaning the wrong informations on the version (and possibly removing history).
Thanks in advance, Dario
You could try the scripts (but not on production data) posted by Paul MIller in the following thread https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014850487 |
Re: Copy Module Without Baseline and History Info PekkaMakinen - Mon Apr 10 08:23:29 EDT 2017 You could try the scripts (but not on production data) posted by Paul MIller in the following thread https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014850487 Hello, Thanks PekkaMakinen, I tried both the methods. The Partitions method is exactly what I need but in the definition of the partition I have to select each single module to add, it is a very strange constraint: I have to add all the modules in a specified Directory of a Project (almost 50 nested modules) and the utility does not allow to add "Directories" (meaning all the modules inside)... The Paul Miller scripts are useful to copy a single module and not groups of modules linked each other, the utility copies the in/out links from/to the original modules. In my context I have to copy group of modules linked each other preserving the link between the copied modules and only between these (no link with the original modules). Example. I have to copy module A and module B, A has links towards B (A->B) I open module A, launch utility, have "A_copy" that as out links to B. I open module B, launch utility, have "B_copy"that as in links from A and A_copy After the execution I will have: A->B, A->B_copy, A_copy->B,A_copy->B_copy all linkset in the same original link module. What I would: A->B, A_copy->B_copy. Linkset of A->B in the original link module, Linkset A_copy->B_copy in a new link module. |
Re: Copy Module Without Baseline and History Info Dario_Imparato - Tue Apr 11 11:03:58 EDT 2017 Hello, Thanks PekkaMakinen, I tried both the methods. The Partitions method is exactly what I need but in the definition of the partition I have to select each single module to add, it is a very strange constraint: I have to add all the modules in a specified Directory of a Project (almost 50 nested modules) and the utility does not allow to add "Directories" (meaning all the modules inside)... The Paul Miller scripts are useful to copy a single module and not groups of modules linked each other, the utility copies the in/out links from/to the original modules. In my context I have to copy group of modules linked each other preserving the link between the copied modules and only between these (no link with the original modules). Example. I have to copy module A and module B, A has links towards B (A->B) I open module A, launch utility, have "A_copy" that as out links to B. I open module B, launch utility, have "B_copy"that as in links from A and A_copy After the execution I will have: A->B, A->B_copy, A_copy->B,A_copy->B_copy all linkset in the same original link module. What I would: A->B, A_copy->B_copy. Linkset of A->B in the original link module, Linkset A_copy->B_copy in a new link module. Hello Dario, my employer would hurt me if I would not take this opportunity: in case you are interested in a commercial solution for your task: Your requirement sounds very much like the "Branch" feature of our "BranchManager for DOORS". See http://it-qbase.eu/products/branchmanager-for-doors/ for details.
Regards, |
Re: Copy Module Without Baseline and History Info Mike.Scharnow - Tue Apr 11 11:25:25 EDT 2017 Hello Dario, my employer would hurt me if I would not take this opportunity: in case you are interested in a commercial solution for your task: Your requirement sounds very much like the "Branch" feature of our "BranchManager for DOORS". See http://it-qbase.eu/products/branchmanager-for-doors/ for details.
Regards, Thank you Mike but I am not interested in a commercial solution. Regards, Dario |