I ran into the same issue. It seems that Maven works using this setup but it will keep complaining that it can not find the pom file itself. From the documentation I understood that Maven first looks in the parent directory for the pom file. If it can not be found it looks in the local repository. And if that fails it will search the remote repository for the pom file. The warning is only a warning... it does work.
Ivo On 7/17/07, Michael Meyer <[EMAIL PROTECTED]> wrote:
Hi four our company I want to set up a parent pom that defines default versions for plugins (pluginManagement), repository locations and so on. The idea is that I make new releases of this project ever so often. Other people should be able to use this pom in their project by including the following in their top level pom: <parent> <groupId>com.company</groupId> <artifactId>root-pom</artifactId> <version>7</version> </parent> When I try to put this all together I get the following warning in a project that references my root-pom module: [INFO] [site:attach-descriptor] [WARNING] Unable to load parent project from repository: Could not find the model file 'D:\checkout\some-app\..\pom.xml'. for project unknown I read about the relativePath tag but I don't want the people to actually checkout the root-pom. Am I using the parent tag for the wrong thing or have I misconfigured something? Cheers, michael --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
