SCM: Move portion of Component across Project Areas?
We have a handful of eclipse projects within a Component which we'd like to move into a different RTC Project Area/Stream/Component. Maintaining history, etc.
Is there any way to do this? Currently on 1.0.1.1 but will be on 2.0.0.1 soon. |
8 answers
Geoffrey Clemm (30.1k●3●30●35)
| answered Oct 31 '09, 1:01 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
A component can be used/shared by any project area (although a user can
only see it if the component permissions let them). To move a directory tree from one component to another component is possible, and a link is stored back to its old history (so that is not lost), but you need to be aware that changes to files in the old component are not applied to the corresponding files in the new component (change-sets only apply to the component to which that change-set belongs). Cheers, Geoff jasonkissinger wrote: We have a handful of eclipse projects within a Component which we'd |
If you are using the Eclipse client, select the project/folder and from the context menu run "Team > Move in Repository..." then pick a target location in another component.
History is maintained, but as Geoff mentioned, you can't accept old change sets that were created when the files were in the source component after it's been moved. You can however apply them as patches. Cheers, Jean-Michel |
|
Assumed the "Team > Move in Repository..." was the way to go, but when I do that it only shows components in that projects Project Area and/or Stream (unsure as it's 1:1).
Example: Project Area A - Stream A -- Component A --- project foo --- project bar -- Component A2 Project Area B - Stream B -- Component B --- project baz I want to move "project bar" to be in Component B. When I do "Team > Move in Repository" on foo, it shows Component A and A2. When I do that on baz, it shows Component B. So don't see a way to cross the Project Area boundary. What is included in this dialog? Incidentally, permissions on Project Area B (Team Configuration > Permissions > Everyone > Source Control > * ) are enabled. Or are there other permissions that must be enabled? Project A is using the SCRUM template, Project B is using the Simple template. |
|
This is a UI limitation and not an implementation restriction on the server. For now, I'd suggest moving the destination component ownership temporarily to the source project area, move the projects, then move it back.
Cheers, Jean-Michel |
|
Thanks Jean-Michel, but I don't see a way in RTC UI to change component ownership. (We're still on RTC 1.0.1.1) And looked at changing stream ownership, but UI limits that to team areas within the project area holding the stream.
Is this something that'd be easy enough from java api. If so, could you send me some snippets to try out? This is a UI limitation and not an implementation restriction on the server. For now, I'd suggest moving the destination component ownership temporarily to the source project area, move the projects, then move it back. |
*Bump*
I know that this is an old thread but is there support for moving folders/files across components in RTC 3.0? I can't manage to find the method of doing it. Jon |
*Bump* Isn't this what you're looking for? Please provide more detail if you can't see this action or it doesn't do what you expect. If you are using the Eclipse client, select the project/folder and from the context menu run "Team > Move in Repository..." then pick a target location in another component. |
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Sep 23 '11, 3:59 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Yes, it is supported, and the instructions for doing so appear in the
messages earlier in this thread. Was there something unclear about those instructions? (They are for 2.0, but it is the same in 3.0). Cheers, Geoff On 9/23/2011 7:08 AM, jnorman1 wrote: *Bump* |
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.