Hi Tommy, Tommy Svensson wrote:
> My team colleague gets the following error: > > _____________________________________________________ > mvn clean or mvn help:effective-pom gives the following error: > > [INFO] Scanning for projects... > Downloading: > https://.../nexus/content/groups/public/.../.../.../xxx-shared/2.0.26-SNAPSHOT/maven-metadata.xml > Downloading: > https://.../nexus/content/groups/public/.../.../.../xxx-shared/2.0.26-SNAPSHOT/xxx-shared-2.0.26-SNAPSHOT.pom > [ERROR] The build could not read 1 project -> [Help 1] > [ERROR] > [ERROR] The project xxx.xxx.xxx:xxx-shared-install:2.0.26-SNAPSHOT > [(/home/xxx/repos/xxx/xxx-shared/install/pom.xml) has 1 error ERROR] > [Non-resolvable parent POM: Could not find artifact > [xxx.xxx.xxx:xxx-shared:pom:2.0.26-SNAPSHOT in nexus > [(https://.../nexus/content/groups/public) and 'parent.relativePath > [<https://.../nexus/content/groups/public%29%20and%20%27parent.relativePath> > [' points at wrong local POM @ line 5, column 13 -> [Help 2] ERROR] ERROR] > [To see the full stack trace of the errors, re-run Maven with the -e > [switch. ERROR] Re-run Maven using the -X switch to enable full debug > [logging. ERROR] ERROR] For more information about the errors and possible > [solutions, please read the following articles: ERROR] [Help 1] > [http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException > [ERROR] [Help 2] > [http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException > _____________________________________________________ > > The pom it complains about (xxx-shared/install/pom.xml) looks like this: > _____________________________________________________ > <?xml version="1.0" encoding="UTF-8"?> > <project xmlns="http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/xsd/maven-4.0.0.xsd";> <parent> > <groupId>xxx.xxx.xxx</groupId> > <artifactId>xxx-shared</artifactId> > <version>2.0.26-SNAPSHOT</version> > </parent> > <modelVersion>4.0.0</modelVersion> > > <artifactId>xxx-shared-install</artifactId> > <packaging>pom</packaging> > > <modules> > <module>xxx-base</module> > <module>xxx-mb-base</module> > <module>xxx-mb-default-config</module> > <module>infrastructure</module> > </modules> > > </project> > _____________________________________________________ > > There is no <relativePath> in it, nor in any of the other poms in the > whole project structure! > > For me it downloads the first file (maven-metadata.xml) and nothing more, > and then cleans OK. I can also do "mvn install" without problem. > > The > _____________________________________________________ > [ERROR] Non-resolvable parent POM: Could not find artifact > [xxx.xxx.xxxi:xxx-shared:pom:2.0.26-SNAPSHOT in nexus > [(https://.../nexus/content/groups/public) and 'parent.relativePath > [<https://.../nexus/content/groups/public%29%20and%20%27parent.relativePath> > [' points at wrong local POM @ line 5, column 13 -> [Help 2] > _____________________________________________________ > > part seems extremely strange to me. If the <parent/relativePath> element is missing, it's value is by default ".." i.e. the parent is searched in your parent directory when you build and install the project. If you additionally deploy it, then your project artifacts are uploaded to Nexus, but the pom in your parent directory is not, i.e. everyone else accessing the project as dependency will fail the way you are seeing it. > Also note that the actual project being built/cleaned/etc is > xxx-shared:2.0.26-SNAPSHOT!! So maven is actually trying to download the > pom being built!! I've personally never ever seen that behavior before in > my life and I've used maven quite a lot. Are you sure that the GAV of the POM in the parent folder is still the same as the one referenced as parent in your child project? If not and it has been changed at some stage, then Maven will ignore the pom.xml in the parent directory and look in your local repository ... and if it finds there a stale one, Maven is satisfied, but your colleague will never have it and his build will always fail. > Also note that we are building with maven 3.0.x! The biggest difference > between me and my colleague is that I'm running on SUSE and she is running > on Ubuntu, but that shouldn't make any difference. > > Any suggestions are appreciated since I'm out of ideas myself. Hope this gives you some ideas, Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
