It's all about the answers!

Ask a question

moving code between project areas

Norman Dignard (356684162) | asked Jan 13 '15, 2:15 p.m.

We migrated code from Clearcase to a RTC project area, and some work was done in that PA.

Management has in parrallel with the above, created a department PA with team areas beneath it.  They now want the code moved from the original RTC PA to the department PA in one or more team areas.  The original PA had all code under one stream with dirs for each app. Now this is being split into one or more team areas.

Under the new department PA , the user is creating new components and one of the options is to add a component from a different stream/PA.     In doing so, is it creating some form of link in the back end or is it creating a copy of all the files into the new PA?    If its some sort of link  and we subsequently archive/purge the original source PA, what happens?   

Accepted answer

permanent link
Geoffrey Clemm (30.1k33035) | answered Jan 15 '15, 1:30 a.m.
A component does not in any significant sense "belong" to a project area.   Think of it as a global object in the repository, that can be used by any stream/workspace in the repository by someone that has read access to the component.   Read access to a component is determined from the "owner" property of the component (where that property is set to be some project/team area or some user).   Note that a component is listed in the GUI under the project area selected by the "Owner" field of that component ... but that is just to provide some place in the GUI to list it (rather than having one long list of all components in the repository).

So back to your question, when you add a baseline of a component to some stream or workspace, you are just logically creating a reference to that baseline (not a copy).   And since you cannot delete/archive/purge a baseline, you can never "lose access" to that baseline.
Norman Dignard selected this answer as the correct answer

Your answer

Register or to post your answer.