Hi,

We start a project with Delphi (Borland) and ClearCase LT. But we have some
questions about the organisation of are sources codes inside the VOB
directory and the way to manage them. First, with Delphi, the sources codes
are relate to a project file that know the link to the physical files that
the project own. We will have more than one project (Some executable, lot of
Dll) and some files could be share from project. When that is the case, the
project know the link to those files (Ex. c:\Directory1\Directory2). Our
problem is when more than one developer will work on those project. With
clearCase, we have to view, one working view and one integration view, when
we check-in the files from the working view, they are transfert to the
integration view, but the compilation of the project from there was not
correct because the link to the files are still relate to the working view.
We could resolve the problem to put all files below the project, but for
some of them it was not possible. THE QUESTION: Is it possible to share
files in ClearCase ?? If it's possible, we could put a share file below a
project and if we change them, the change is share among project.

Other question: What is the better approach to organise project (Executable,
DLL) in ClearCase ?? My first thought is to have one VOB for each. If we
relate our development process with Rose Models (In the process we develop
components in the implementation view), is it a good way to create a VOB for
each Component ???

Thank you

Yves Gagnon

************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages: 
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************

Reply via email to