My point is that it does not necessarily have to be the parent. You can
have
<dependencies>
<dependency>
<groupid>somegroup</groupid>
<groupid>some-local-only-dep</groupid>
</dependency>
<dependency>
<groupid>ariesgroup</groupid>
<groupid>dep-matrix</groupid>
<type>pom</type>
</dependency>
</dependencies>
The dep-matrix pom would contain the reusable dependencies.
cheers
-thomas
On 12/10/2009 04:13 PM, Lin Sun wrote:
Right, in our case the java5-parent is the parent module of each of
the individal module such as blueprint, jmx, etc. So it makes sense
to me to put the centralized dependency management there.
Lin
On Thu, Dec 10, 2009 at 2:00 AM, Thomas Diesler
<[email protected]> wrote:
I suppose you could create a dependency-matrix module that contains the
project dependencies. Individual projects would have a dependency on that
matrix module. Circular dependencies must of course be avoided.
https://anonsvn.jboss.org/repos/jbossas/tags/JBoss_6_0_0_M1/component-matrix/pom.xml
cheers
-thomas
On 12/09/2009 09:31 PM, Lin Sun wrote:
Hi,
I kinda want to use centralized dependency management in our trunk.
Currently, each of the individual project has its own dependency
manager, for example blueprint, jmx, transaction, etc. And sometimes
we are using the same project but different versions. I'd like us to
use the centralized dependency management so that we can make sure
there is no version conflict and reduces our dependencies.
My initial thinking is to do this in trunk/pom.xml like what we do in
Geronimo, but I realized each of the individual project has
java5-parent as the parent. So seems to me that I would have to put
the centralized dependency management in java5-parent/pom.xml. Does
that sound right or anyone has a better approach?
Thx
Lin
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler JBoss OSGi Lead JBoss, a
division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx
