Common code across multiple projects

[thomas . maciejewski]

I have a related question to this to which I am seeking an answer.

I have two projects: ProjectA and ProjectB
both of them use part of a common code base that is in a project called:
Common

I would like to set up CVS that I can have a reference to Common shared by
both ProjectA and ProjectB
something like:

ProjectA/Common
ProjectB/Common

and common being in its own project:
Common

Common code should be able to grow on its own and the current development
branches and main trunk of ProjectA and ProjectB should see these changes.
I should be able to go into ProjectA/Common and make a change and commit
and when I update from ProjectB I should see these changes.

However when I create a production branch I want to have have my own copy
of common.
That is,  once I do the production branch and then make a production bug
fix
to ProjectA/Common I do not want it to show up in Common nor in
ProjectB/Common

I tried to do this via & modules but I found that even when I branched
ProjectA common
was not also branched within there so if updated the branch I would get the
current development
version of Common and if I check in a production bug fix it would then be
part of the main production branch

Does anyone have a solution to this?

I am sure this is fairly common to most companies that have multiple
projects but wish to have code re-use

Tom





**********************************************************************
The information contained herein is confidential and is intended solely for the 
addresse(s).  It shall not be construed as a recommendation to buy or sell any 
security.  Any unauthorized access, use, reproduction, disclosure or 
dissemination is prohibited.
Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall assume 
any legal liability or responsibility for any incorrect, misleading or altered 
information contained herein.
**********************************************************************