If you want to break the code base up into multiple projects then the
shared code would go in one project and the product specific code for
each product would go into its own project with a dependency on the
shared code project. The projects in Eclipse would map to a directory in
subversion. The shared code project might be more than one project (one
per jar produced) or a single project that produced multiple jar
artifacts for the other products to use. Any particular Java file would
only live in one place and would used as part of a jar at runtime.
During development the product projects would depend on other shared
projects (rather than a jar file) which would facilitate debugging
across projects (without attaching source to a jar) or re-factoring
The Struts project is made up of several sub-projects with various
dependencies on each other. Each sub-project is intended to be able to
do there own independent releases and so they have their own
trunk/tags/branches directories. svn:externals are used on the /current
directory to present a simpler directory structure for the trunk
directories of all the sub-projects.
Spring is a project that puts all of its code in a single src tree and a
single Eclipse project but builds several different jars.
In both cases for Struts and Spring, a directory in the repository maps
to a project. With Struts you could have Eclipse projects for each
struts sub-project or you could put everything in one Eclipse project
using the /current svn:externals directory.
What is the advantage you get out of having a single source tree for all
the products when it seems like people work on them and think of them as
From: Meme Bag [mailto:firstname.lastname@example.org]
Sent: Monday, April 04, 2005 6:17 PM
Subject: Re: Problem with "Use specified module name:"
I'm curious about popular approaches Subclipse users take to the issue
of multiple products built from the same code base. When I used CVS in
the past I did the same thing I'm doing with SourceSafe (ant fetching
different CVS directories under the current working directory.)
How do Subclipse users share source code among multiple products? Do
they build different subsets of a single Subversion tree in each Eclipse
Jeff Bowden <email@example.com> wrote:
This is a subclipse issue. If he didn't need eclipse/subversion
integration then his ant script could just do the checkouts and
and subversion would deal with things just fine by themselves.
true that the 'correct' subversion way to do things is to use
svn:externals but it would sure be nice if subclipse could
handle subdirectories with different URLs.
Do you Yahoo!?
Better first dates. More second dates. Yahoo! Personals
Received on Tue Apr 5 08:49:29 2005