> cc
>
> Veuillez Objet
> répondre à Re: [m2] 's
> Maven Users List
> <[EMAIL PROTECTED]
>
cc
VeuillezObjet
répondre à Re: [m2] 's
Maven Users List
&
e. Thanks again for your help.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Sunday, November 06, 2005 8:37 PM
To: Maven Users List
Subject: Re: [m2] 's
The docs on are lacking, and it really makes it quite
deceptive. It is not from m1.
What it does
ied below, or must the parent POM be in the
> repo? Does MNG-740 have any merit?
>
> Are there doc/clarification notes on and I just missed it?
>
>
> -Original Message-
> From: Jeff Jensen [mailto:[EMAIL PROTECTED]
> Sent: Sunday, November 06, 2005 8:08 AM
> To:
ust missed it?
-Original Message-
From: Jeff Jensen [mailto:[EMAIL PROTECTED]
Sent: Sunday, November 06, 2005 8:08 AM
To: 'Maven Users List'
Subject: RE: [m2] 's
Thanks Dan,
My problem seems similar/same as your MNG-740. I too have the parent pom
not in a dir directly a
setting seems to have no effect. I do not receive
an error message that the parent was not found either.
I'll add my use case to the comments. Thanks again Dan.
-Original Message-
From: dan tran [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 05, 2005 11:52 PM
To: Maven Users L
Normally, maven looks for parent pom with this order
immeditate parent directory
local repo
remote repo
So the parent pom.xml in parent dir, must have the groupID and artifacID
found in child pom
But there is a bug that may be your problem too
http://jira.codehaus.org/browse/MNG-740
-D
O
