UCM Projects and common codeMy approach would be to put this directory in
it's own component VOB and create a project out of it. Then this component
would be shared read-only with the other projects. Everytime he updates his
code, he creates a new baseline to which the other projects rebase their
integration streams. Don't know how easy it would be to do this after the
fact, though. UCM isn't very graceful when it comes to splitting VOBs. Wish
I had done this with some of our VOBs. Isn't hindsight a wonderful thing?
HTH
Matt
-----Original Message-----
From: owner-cciug@rational.com [mailto:owner-cciug@rational.comOn Behalf
Of Ghassan Hammouri
Sent: Friday, July 27, 2001 7:53 AM
To: CCIUG (E-mail)
Subject: [cciug] UCM Projects and common code
Hi,
We have a number of UCM projects, all of which share a critical directory
that contains code common to all projects. This code is written by only one
person. That person is getting sick and tired of having to merge his stuff
to the integration streams of the other projects (about 10 merges required).
He just want to update the code and have it automatically appear in the
integration streams of the other projects.
I don't know if this is feasible in ClearCase/UCM. Any suggestions?
Regards,
Ghassan
SS8 Networks
(613) 592-2100 ext. 3411
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Tue Jul 31 2001 - 22:04:03 EDT