The relative path is used when building a child module to find the parent. By default it looks in ../pom.xml but you can change this. If the matching parent is not found on disk, it will be retrieved from the repository.
You should not have properties in the g/a/v of either the parent section or the primary declaration of an artifact (project.group...etc) as this will surely cause you lots of headaches. -----Original Message----- From: Dobri Kitipov [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 7:50 AM To: [email protected] Subject: Maven 2.0.7 and <relativePath/> Hi all, I did not find a good explanation about the usage of <relativePath/> in the net. I am interested if I have e.g.: <parent> <groupId>com.mycomp</groupId> <artifactId>mycomp-parent-pom</artifactId> <version>${mycomp.version}</version> <relativePath>../../parent-pom/pom.xml</relativePath> </parent> If the <relativePath> will be checked first and then the repositories? Currently I can see into the logs that Maven tries to download the artifact from the repository, but there is no an artifact with version ${mycomp.version}. I am expecting that Maven should try the relative path? Thank you in advance. Regards, Dobri --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
