Can the ClearCase version importer and ClearCase synchronizer be used together?
Accepted answer
2 other answers
Comments
I agree with this answer, but for folks who are interested in the details, I will speculate a bit (I haven't confirmed any of these speculations by testing or reviewing the code).
The importer shares a lot of code from the synchronizer, so there is a reasonably good chance that the importer just re-used the synchronizer mechnism for linking an RTC file/directory item to a ClearCase file/directory element.
If that is the case, then after importing a bunch of code, you can create a synchronization stream against that imported code, and start two-way synchronizing between RTC and ClearCase. But I believe the importer has no knowlege of which particular version the synchronizer has imported, so if you ran the importer after synchronizing, the importer would not re-use any of the versions imported by the synchronizer, but instead would import its own copy of those versions, so you'd end up with two versions ... one imported by the synchronizer and another by the importer.
So unless you are very careful, your users will get confused, which is why I believe Abraham's answer is the correct one (:-).
Using ClearCase Version Importer and ClearCase Synchronizer together is not supported.
If you force to run them, you would see different versions for Version Importer and Synchronizer as written in Geoff's comment.
Comments
I believe that the CC synchronizer doesn't care whether or not versions have been imported by the CC importer ... it just will synchronize back to ClearCase whatever versions are currently selected by the synchronization stream. But note that I don't think you can tell the CC importer to attach what is importing to some existing version in RTC that was not brought over by the CC importer ... e.g., if M1 has been brought over by the synchronizer, you cannot tell the importer to attach F1 off of M1. (Yoshio: Please correct me if I'm wrong about that).