RE: RE: Multiple Projects that make up a Product
From: Anderson, Aaron <AndersonA_at_gsicommerce.com>
Date: Thu, 29 May 2008 12:34:07 -0400
Another question to ask is why you are dividing up the master product into components... Some people do this because they want to organizationally control who works on which pieces, but they are all rev'ed and released at the same rate - at which point the directory structuring below works.
Some people split up into components because they want to release the different components at varying velocities. If you are doing this, then you really have a dependency management issue and you probably want to look into something like using Maven or Ant/Ivy to force your build process to pull specifically published versions of the components together to assemble builds that you want. Using SVN externals or directory structuring won't work so well for this.
- Aaron Anderson
-----Original Message-----
Hi Chris,
Your question is an interesting topic of discussion.
You need to design your repository organization and adapt your build system around it.
If you are making a Product, composed of several "components" (those pieces that create the jar files, but it could be composed of DLLs, jars, config files, etc) and you are just interested on building the Product as a whole entity, then you may consider to organize your repository in a single Project, still with different "components" that are build independently.
/TheProduct
In this way, you track your entire product as a single project that contains all the code. You can build the previous version just by getting a tagged release.
In the original repository organization shown in your message, you would need to tag the version that you released. That is not too bad.
/components
With this approach you can release each component as an independent library...but if you are not sharing built components with other teams, I don't see the benefit of tracking at such fine-granularity.
I am new to Subversion, I used Accurev before.
-Jorge
___________________________
Hello all,
So, I have multiple projects
repo/
Now I want to make a build of the product that will be compiling project 1 and project 2 into jar files and package them for the product. I can see how managing this could get real crazy... All of a sudden project1 has several branches and project 2 has several branches and I need to provide a build script that know which ones to pull into the project.
Has anyone done something like this before and is there a better way to manage it?
Thanks,
-- The Hardest thing in the world to do is Think, Mark Twain --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org For additional commands, e-mail: users-help_at_subversion.tigris.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org For additional commands, e-mail: users-help_at_subversion.tigris.orgReceived on 2008-05-29 18:34:33 CEST |
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.