It is not needed to have a parent pom just for dependencies. You just
need an artifact of packaging pom where you declare your dependencies,
and then add a dependency to this artifact. As normal dependencies are
transitive, this lets you combine several dependency sets.
If there are special needs, you may also have a look at the 'import'
scope introduced in Maven 2.0.9, although in general I would recommend
the "old" way.
Stefan
Raffaele wrote:
Hi all,
I have the following short question:
should be possibile define a pom with two or more parent pom?
A practical utilization:
It would be useful having a pom which specifies db specific dependencies and
a pom which specifies web specific dependencies, and my app could be child
of both those pom(s).
Thanks in advance,
best regards
Raffaele
--
best regards,
Stefan Seidel
software developer
________________________
VUB Printmedia GmbH
Chopinstraße 4
D-04103 Leipzig
Germany
tel. +49 (341) 9 60 50 07
fax. +49 (341) 9 60 50 92
mail. [EMAIL PROTECTED]
web. www.vub.de
HRB Köln 24015
UStID DE 122 649 251
GF Dr. Achim Preuss Neudorf,
Dr. Christian Preuss Neudorf
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
