On Friday 06 August 2004 11:36 am, Anastasios Angelidis wrote: > >The general approach is to set up a separate "component" in source > >control for each component of your code that can be depended upon. All > >modern source control systems allow you to label branches, so you can > >have a DB1_1.0 label for database 1 code version 1.0. Product 1 can > >depend on this. Then as you make further changes you label is DB1_1.1 > >or maybe DB1_2.0 as you wish, and you change dependencies accordingly. > >Product 1 can still depend on 1.0 if it wishes, and you can still make > >changes in the 1.0 branch. > > But what happens, when both products depend/share functionality on this > component simultanously.
Don't forget how java "shares" code: jar files If you build your shared functionality into a jar, you can deploy that jar in support of that functionality. Building different versions of a particular shared code base is simply a matter of extracting a particular branch of source and performing the build. Bob --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
