cc
VeuillezObjet
répondre à Re: [m2] parent's relativePath
Maven Users List
VeuillezObjet
répondre à Re: [m2] parent's relativePath
Maven Users List
[EMAIL PROTECTED]
che.org
The docs on relativePath are lacking, and it really makes
Subject: Re: [m2] parent's relativePath
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
on relativePath and I just 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] parent's relativePath
Thanks Dan,
My problem seems similar/same as your MNG-740. I too have the parent pom
To: Maven Users List
Subject: Re: [m2] parent's relativePath
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
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] parent's relativePath
The docs on relativePath are lacking, and it really makes it quite
deceptive. It is not extend from m1
Hi,
In parent, how does one use relativePath? I can only get POM
inheritance to work if I have done a mvn install on the parent project.
Then the component projects find it in the local private repo.
I'm sure I just don't understand something yet. If there is docs on it,
please give me an RTFM
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
