We have aggregation projects that build a jar file containing all the
dependencies for that set of libraries.
We exclude anything that is being provided in another library so we know
exactly what version of transitive dependencies are being used.
I finally wrote up a description on our technica
You can create a pom project declaring those dependencies and then add a
dependency toward that pom project in each project (don't forget to
specify pom when declaring that dependency.
Cheers,
Guillaume
Le 28/09/2011 06:52, Behrang Saeedzadeh a écrit :
Thanks for affirming this Ron. By the way
Thanks for affirming this Ron. By the way, how do you ensure that all
those projects depend on the same set of external dependences without
duplicating the information for each POM?
Cheers,
Behrang Saeedzadeh
http://www.behrang.org
On Tue, Sep 27, 2011 at 2:17 AM, Ron Wheeler
wrote:
> I agree.
I agree.
4- better visibility into the project for the manager. You know which
modules are being changed and which ones are supposed to remain
unchanged. You also get a bit of a warning about scope issues or
potential problems when a new module gets added to the list of things
that need chang
Hi,
For large projects, wouldn't multiple single module projects work better
than one multi-module project, because:
1- when using a dvcs, the repositories tend to become very large and when
the project is divided into multiple single module projects, each project
can have a small dvcs repository
