Thanks Dan, My problem seems similar/same as your MNG-740. I too have the parent pom not in a dir directly above the other components, but in a dir at the same level as the other components.
In MNG-740, "A" doesn't build for me without the listed step 1: install root POM. The <relativePath> 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 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 be your problem too http://jira.codehaus.org/browse/MNG-740 -D On 11/5/05, Jeff Jensen <[EMAIL PROTECTED]> wrote: > > 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 link! TIA > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
