On Thu, 24 Jul 2008 07:31:47 Michael McCallum wrote:
> On Thu, 24 Jul 2008 07:15:48 Thomas Darbois wrote:
> > The best way to avoid that problem is to use a parent pom that define
The problem with parent poms is that they are versioned resources but people
make use of the 'ignore the version just use the ../../pom.xml' parent with
modules and inheritance. You end up using the parent on trunk/head. As a
result you have no consistency.
if you release your entire source tree each time then you ensure consistency
but you lose all of the power of having prebuilt artifacts esp for larger
teams.
One key factor that people seem to forget is that when you composite
dependencies each of those dependencies can have a different inheritance
hierachy...
for a very simple contrived example...
parent 1 and 2 and 3 are released over time
a :: parent 3
-> b
-> d
b :: parent 2
-> e
-> c
c :: parent 1
d :: parent 2
e :: parent 2
now if you resolve your dependencies for 'a' you get
a (parent 3)
-> b (parent 2)
-> e (parent 2)
-> c (parent 1)
-> d (parent 2)
if order for b, e, c and d to be consistent you have to honour their
inheritance...
i'll leave all the implications to the unfortunate reader ;-)
--
Michael McCallum
Enterprise Engineer
mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
