Non-resolvable parent POM: When building Maven 3 Project Site

Question

I am currently facing the following problem with Maven 3 when I am trying to build the site. I will appreciate you help on this.

mvn clean site

Answer 1

The problem is not in your pom files. When I built your aggregation-pom, Maven downloaded normally the parent-pom from the remote repo (after I deleted from my local repo).

Try this:

mvn -U clean install site dependency:purge-local-repository

Additionally, you could do some clean up:

• remove <relativePath/> from all of them
• remove <version>0.1-SNAPSHOT</version> and <groupId>my.com</groupId> from projA and ProjB (they are inherited from the parent)

Answer 2

As pointed out by this answer, there is a bug in the site plugin, which only looks for dependencies in what it thinks is Maven central.

I am having the same problem in Maven 3.0.4 and site-plugin 3.3 . I also have the issue that it works in my development machine which is running Windows 7, but not in the CI-Server which is running Jenkins on Debian.

Answer 3

I got the same problem... works on my developer MacBook, but fails on my Jenkins running on RHEL7 when running mvn site using maven-site-plugin:3.7. I did not test to downgrade the site plugin.

I found another solution. The problem in my case was the maven-project-info-reports-plugin especially the goal dependencies. If I skip the goal with -Dmpir.skip=true my site get's generated (without the dependencies :( report).