Ray, I'd suggest placing the "common" or "library" packages that you're
using across projects in their own "cvs modules", with their own build
scripts that produce one or more jars for each package. Then reference the
library jar(s) from your "projects". This ought to save you some build
time, too - you won't be building or checking out the common or library
packages with each build.
If you need to package the library jars with your project for delivery,
your ant build descriptor can be crafted to copy the jar from its location
into a temporary directory in order to be tarred or zipped into a
distribution. Take a look at Ant's own build descriptor for a good example
of putting together a binary or source distribution.
HTH,
Ken
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
