+1.
Maven 3 includes improvements about parent pom handling. See
http://docs.codehaus.org/display/MAVENUSER/Iron+Fist+of+Maven+3.0+transition+pack#IronFistofMaven3.0transitionpack-relativepathtoparent
I suspect you're referring to a pom that's just not in the parent directory.
In maven 2, this is
To: Maven Users List
Subject: Re: Maven 3 project ordering
+1.
Maven 3 includes improvements about parent pom handling. See
http://docs.codehaus.org/display/MAVENUSER/Iron+Fist+of+Maven+3.0+transition+pack#IronFistofMaven3.0transitionpack-relativepathtoparent
I suspect you're referring to a pom that's
I'd like to do at my
current place), I'd NOT need that relativePath tag, correct?
-Original Message-
From: bmat...@gmail.com [mailto:bmat...@gmail.com] On Behalf Of Baptiste
MATHUS
Sent: Tuesday, August 24, 2010 3:38 AM
To: Maven Users List
Subject: Re: Maven 3 project ordering
+1
Thank you all!
-Original Message-
From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of
Anders Hammar
Sent: Tuesday, August 24, 2010 9:06 AM
To: Maven Users List
Subject: Re: Maven 3 project ordering
That would be correct, as that pom artifact (the parent
Hello again list - was hoping to NOT be sending all these maven 3
questions...but.
So we have a parental pom that listed as the top module in the top level pom.
In maven 2, the build just chugs along successfully and handles this no problem.
In maven 3, however, somehow maven jumps right
If you set the relativePath element for the parent section, does it make a
difference?
/Anders
On Mon, Aug 23, 2010 at 18:03, EJ Ciramella ecirame...@casenetinc.comwrote:
Hello again list - was hoping to NOT be sending all these maven 3
questions...but.
So we have a parental pom that
Maven 3 defines a strict ordering of how agrregation and parents interact.
Benjamin might be able to recall the exact ordering rules as he implemented
them.
I suspect this is what it catching you out
-Stephen
On 23 August 2010 17:03, EJ Ciramella ecirame...@casenetinc.com wrote:
Hello again
