I did not tried to install but shouldn't it work without installing? At least that what I understand from the docs. And I tried adding the relativePath but it did no difference as I am using the default value, so omitting gives the same result. Em 31/10/2011 18:38, "G. Gustavo Pollitzer" <[email protected]> escreveu:
> On 31/10/2011 5:01 PM, Rafael Ribeiro wrote: > >> Hi all, >> >> I am having issues regarding parent pom resolution in maven 3. I am >> aware that some changes were made in order to make it stricter and less >> problematic as pointed out in https://cwiki.apache.org/** >> MAVEN/maven-3x-compatibility-**notes.html#Maven3.**xCompatibilityNotes-** >> ParentPOMResolution<https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ParentPOMResolution>but >> I am having exactly the issue that should have been fixed. >> My build only works if invoked from parent pom directory and note that I >> use exactly what is described as the default structure (parent pom on >> parent directory). If instead I try to build the dependant project only it >> fails complaining that it cannot find parent pom (as it were a dependency >> of the other module I really depend on). >> I am sending a sample I developed in case anyone can help me finding >> what I could possibly done wrong (and sincerely I made it so simple that I >> cannot find anything that could be changed). >> >> best regards, >> Rafael Ribeiro >> >> >> ------------------------------**------------------------------**--------- >> To unsubscribe, e-mail: >> users-unsubscribe@maven.**apache.org<[email protected]> >> For additional commands, e-mail: [email protected] >> > Is the parent artifact already in your local repository. If its not, > install it if possible, or use the <relativePath> element inside the > <parent> element in your child projects. Perhaps this solves your problem. >
