Chris Gilliam wrote:
> I am new to SVN and have a question about how to setup and manage a
> repository. We are building an Enterprise Level application that will
> have multiple projects that will be compiled into Jars and the group of
> Jars will make up the Product. When I look at the SVN documentation
> about multiple Projects in SVN it seems straight forward. However, the
> documentation doesn't lend itself to the product level.
>
> So, I have multiple projects
>
> repo/
> -project 1
> - branches
> - trunk
> -project 2
> - branches
> - trunk
>
>
> 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?
One approach is to make a product-level entry that has your
build/packaging scripts and a set of external references to pull in all
of the components. During development you may want to let these
reference the head of the projects trunk or branch work, but for
releases you would point them to tag copies of each component. This
level can also have its own trunk/branch/tag structure for simultaneous
versions, and it doesn't really matter if the components live in the
same repository or not.
--
Les Mikesell
lesmikesell_at_gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-05-29 17:18:31 CEST