[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Maintaining separate revision numbers for dependent projects

From: Matthew Kidd <Matthew.Kidd_at_cappsdigital.com>
Date: 2006-11-15 04:50:07 CET

Hi,

My team is beginning a project tomorrow for a complex project in which 3 separate code bases form the basis of the overall project. Each code base operates a different facet of the application but in the current CVS the hieracrhy is as such:

project A
   |
   |
   |
   |Subproject A
        |
        |
        |
        |Codebase
   |
   |
   |
   |Subproject B
        |
        |
        |
        |Codebase
   |
   |
   |
   |Subproject C
        |
        |
        |
        |Codebase
   |
   |
   |
   |more pertinent files and folders

Now as I was saying before each of these code bases is dependent on the other but can function separately. I'm trying to maintain as much of the previous project structure as possible but as I'm sure you're all away, if I were to put project A in SVN the subprojects would all have the same revisions even if those code bases are stable.

Does anyone know how I can maintain the above project hierarchy for porject A yet have independent revisions for the subprojects?

Matthew Kidd

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 15 04:50:17 2006

This is an archived mail posted to the Subversion Users mailing list.