How to disconnect the component between different projects
I am trying to create a new project (Project_New) with the latest code in an old project (Project_Old) - to train the new developers to get familiar with the code . Here is what I am trying to do:
- Create a snapshot for the dev stream of Project_Old
- Open the snapshot
- Create a new stream (under Project_New) using the snapshot.
However, I noticed that the components are actually "shared". For example, if I rename the component in Project_New (Or I change the owner of the component), the one in Project_Old is also changed. Is there a way to disconnect the components in the two projects? i.e., I'd like to totally treat them as separated projects.
Accepted answer
The component name affects all instances of the component. The name should represent what is stored in it, not the version of what is stored. When the component is in a stream or workspace, it can have different configurations of change sets. That configuration doesn't necessarily have to be a certain version.
If you really want a different component name, you can create a new component. However, you have to copy the contents to the new component and you will lose history and merging changes to the old component isn't possible.
If you really want a different component name, you can create a new component. However, you have to copy the contents to the new component and you will lose history and merging changes to the old component isn't possible.
Comments
