migrating ClearCase UCM multicomponent vobs with intervob l
I'm evaluating a possible move to RTC from ClearCase UCM. Migrating the existing codebase, while maintaining the existing components, is required. We use multicomponent vobs with intervob links, so the top-level file structure in a CC view is crucial.
Here is a typical example, components marked with *. (I understand symbolic links are not currently supported - but are a top priority).
I thought view_root would be the elipse project workspace in RTC. But I just can't figure out how to do this. I would be very grateful if somebody can show me a (painless) way to set up this structure. Regards, David |
22 answers
After step 2, what projects were found and loaded? The two componets, comp1 and comp2, were identified as "projects" and loaded. I create the new file with "new file" in windows explorer in the root directory of comp1, next to the .project file. But I showed you all this with screendumps in the email... |
David.Sedlock.infineon.com wrote:
I create the new file with "new file" in windows explorer in I'm guessing that's the issue. When you create a file in the file system rather than within Eclipse, then Eclipse doesn't always know about it, at least not right away. And if Eclipse doesn't know about the file, then RTC doesn't know about it either. In your IDE, right click on the comp1 project and select Refresh. Does the new file show up? Instead of creating the file in the file system, try creating it within Eclipse (File > New > File). Does it show up in that case? |
David.Sedlock.infineon.com wrote: "at least not right away" I think you mean never! I could find no refesh button (and I tried many!) that made this file show up. It finally does show up when I create it explicitly in Eclipse. But it's unreasonable to expect people to create new files like this one at a time in a GUI. Please explain the right way. |
I finally found the place: the refresh in the workspace tab displays the new file. Once that is refreshed, the Pending Changes tab shows it as an unresolved change. Whew!
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Aug 05 '09, 8:53 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
You need to go to the package explorer view, and select "Refresh" there.
I've submitted work item 89264 to get the Pending Changes view to provide a "refresh" option that scans the sandbox for changes. Cheers, Geoff David.Sedlock.infineon.com wrote: David Olsenwrote: |
Either the idea of the "current changeset" is not working or I don't understand how it works. To try out the suspend functionality I wanted to create two changesets, make some changes to a file with the first, check the file in, then make some more changes with the 2nd and check in. Then I wanted to suspend the 2nd change set (which should also suspend the first).
I carefully ensured that the 2nd changeset was set as current before I made the 2nd changes and checked in, but it is clear the new version is in the first change set. For example, in the Pending changes view the 2nd changeset shows no files. Furthermore, the History view of the file does not show the 2nd changeset. What am I doing wrong? |
Suspending change-sets works like this:
Make some changes, check them in. Suspend that change-set. Make some other changes, check them into a different change-set. Then you'll see the "current" version of the file is from the 2nd change-set. -- Brian Nelson Jazz ClearCase Connector Team "David.Sedlock.infineon.com" <David> wrote in message news:h5ekji$4m4$2@localhost.localdomain... Either the idea of the "current changeset" is not working or |
Geoffrey Clemm (30.1k●3●30●35)
| answered Aug 06 '09, 9:56 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi David,
I just tried this out in a fresh RTC-2.0 repository, and it worked fine for me. How did you do your second checkin? Did you: - have "auto-checkin" on (i.e. every save results in a checkin) - use the "checkin-all" operation - use the "checkin" operation If you did auto-checkin or checkin-all, I have no explanation (:-). If you did a "checkin" operation, you are required to select which change set you want to checkin to ... (one of the existing ones, or a new one) ... is there a chance you selected the first change set (it will be the first entry in the list)? Also, when you looked at the history of the file, did it show two changes (in the same change set), or just one change? If there is just one change there, then the second checkin didn't happen ... Cheers, Geoff David.Sedlock.infineon.com wrote: Either the idea of the "current changeset" is not working or |
I did it all carefully again and it really is not working.
"auto-checkin" is NOT on. I used "checkin-all" operation with the Unresolved folder selected. I carefully ensured that the 2nd changeset was marked as default. This showed up clearly in the GUI. The 2nd change is clearly associated with the 1st changeset. The history of the file does NOT show the 2nd changeset. And the 2nd changeset shows no files associated with it in the ChangeExplorer. Suspending the 1st changeset backs out both changes. |
When I try to explicitly checkin against the 2nd changeset, I get the msg "cannot checkin because file is being changed in another active changeset". But the 2nd changeset is clearly marked as current!
OK, I found it: Note: A file or folder in a component cannot be part of more than one active change set. When a file or folder is included in an active change set, all changes to it become part of that change set whether or not the change set is current, and changes to that file or folder cannot be explicitly checked in to a new change set until the active change set that includes it is completed. So, despite the fact that a different changeset is current, if I continue to change a file that has already been changed against some other changeset, the changes continue to be charged to it until it is completed. If I were to change a different file, which was not in the first change set, the changes would go into the current one. I can understand the reasons behind this, but probably some extra care is needed - e.g. a message that the current changeset is not being used because of this rule. |
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.