Can't build the project with Maven

[vincentx]

Got an error message while running mvn -Dcrx.host=localhost -Dcrx.port=4502 -PautoInstallPackage clean install

[ERROR] Unresolveable build extension: Plugin com.day.jcr.vault:content-package-maven-plugin:0.0.20 or one of its dependencies could not be resolved: Failed to read artifact descriptor for com.day.jcr.vault:content-package-maven-plugin:jar:0.0.20: Could not transfer artifact com.day.jcr.vault:content-package-maven-plugin:pom:0.0.20 from/to adobe (http://repo.adobe.com/nexus/content/groups/public/): peer not authenticated -> [Help 2]

[vks2009]

I am getting the same issue. do we have any update on this

[jayproulx]

Same issue here.

[joerghoh]

Where do you get this exception? It's not clear if you just cannot download the content-package-maven-plugin artifact or if you try to upload something to this path. Of course the upload thing should fail.

Anyway, I updated the content-package-maven-plugin to version 0.0.24, can you update and try again?

[jayproulx]

The issue I was having the other day seems to be unrelated. Apparently the 1.6 JDK I was using had an old certificate chain that made the repo.adobe.com repo SSL cert look invalid. I've upgraded to the latest JDK8 (since AEM 6.0 SP1+ now officially supports JDK8) and my builds are now all succeeding.

[cyface]

This is happening for me again, it looks like there is a POM file missing?

[INFO] Downloading: https://repo.maven.apache.org/maven2/com/day/jcr/vault/content-package-maven-plugin/0.0.24/content-package-maven-plugin-0.0.24.pom
[WARNING] The POM for com.day.jcr.vault:content-package-maven-plugin:jar:0.0.24 is missing, no dependency information available

When I go to that URL, I see a 404...

That repo is definitely broken. I found that I had to force the adobe rep by explicitly including the adobe-public profile on my run line:

mvn clean install -P autoInstallPackage adobe-public

[ichirital]

I ran into the same issue at a customer trying to install a developer's workstation on Windows.
They have a proxy set up so added that into the settings.xml, still not much use.

In the end, we realised that out parent pom.xml already had the repositories section defined (lazybones project structure) and thus we just left the settings.xml that came out with the Maven fresh install + proxy config and it all works as expected.

<!-- Inclusion of repositories in POMs is controversial, to say the least. It would be best if you proxied the Adobe repository using a Maven Repository Manager. Once you do that, remove these sections. --> <repositories> <repository> <id>adobe</id> <name>Adobe Public Repository</name> <url>https://repo.adobe.com/nexus/content/groups/public/</url> <layout>default</layout> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>adobe</id> <name>Adobe Public Repository</name> <url>https://repo.adobe.com/nexus/content/groups/public/</url> <layout>default</layout> </pluginRepository> </pluginRepositories>

Not completely sure why the other option won't work as it looks like maven still tried to pick up some of the "fallback" repositories instead of the Adobe one, even with the explicit forcing in the mvn clean install command as suggested above.

Hope this helps.