Maven "peer not authenticated" errorcom/day/jcr/vault/multimodule-content-package-archetype while generating archetype | Community
Skip to main content
jayproulx
jayproulx
Level 2
October 16, 2015
Solved

Maven "peer not authenticated" errorcom/day/jcr/vault/multimodule-content-package-archetype while generating archetype

  • October 16, 2015
  • 9 replies
  • 10098 views

I've tried generating a project from an archetype this morning, and I'm getting the following results.  I've also seen other errors trying to build an existing project, but I'll start here as this is probably the easiest entry point.  I've tried a few things, from using http://repo.adobe.com (as specified in the settings on that page), to specifying https://repo.adobe.com, installing the SSL cert locally and trusting it, etc. I can download quite a few dependencies from repo.adobe.com, but some of them fail with this error message.

Here's the error:

jproulx-mpb15r:temp jproulx$ cat ~/.m2/repository/com/day/jcr/vault/multimodule-content-package-archetype/1.0.2/multimodule-content-package-archetype-1.0.2.jar.lastUpdated #NOTE: This is an internal implementation file, its format can be changed without prior notice. #Mon Apr 20 15:00:44 EDT 2015 default-http\://repo.adobe.com/nexus/content/groups/public/.lastUpdated=1429556443809 http\://repo.maven.apache.org/maven2/.lastUpdated=1429555415785 default-adobe-public-releases/.lastUpdated=1429555439318 default-https\://repo.adobe.com/nexus/content/groups/public/.lastUpdated=1429556444161 http\://repo.maven.apache.org/maven2/.error= adobe-public-releases/.error=Could not transfer artifact com.day.jcr.vault\:multimodule-content-package-archetype\:jar\:1.0.2 from/to multimodule-content-package-archetype-repo (adobe-public-releases)\: No connector available to access repository multimodule-content-package-archetype-repo (adobe-public-releases) of type default using the available factories WagonRepositoryConnectorFactory https\://repo.adobe.com/nexus/content/groups/public/.error=Could not transfer artifact com.day.jcr.vault\:multimodule-content-package-archetype\:jar\:1.0.2 from/to adobe-public-releases (https\://repo.adobe.com/nexus/content/groups/public)\: peer not authenticated http\://repo.adobe.com/nexus/content/groups/public/.error=Could not transfer artifact com.day.jcr.vault\:multimodule-content-package-archetype\:jar\:1.0.2 from/to multimodule-content-package-archetype-repo (http\://repo.adobe.com/nexus/content/groups/public/)\: peer not authenticated

Here's the output from the example command line from https://docs.adobe.com/docs/en/aem/6-0/develop/dev-tools/ht-projects-maven.html

jproulx-mpb15r:temp jproulx$ mvn archetype:generate     -DarchetypeRepository=http://repo.adobe.com/nexus/content/groups/public/     -DarchetypeGroupId=com.day.jcr.vault     -DarchetypeArtifactId=multimodule-content-package-archetype     -DarchetypeVersion=1.0.2     -DgroupId=my-group-id     -DartifactId=myproject     -Dversion=1.0-SNAPSHOT     -Dpackage=com.mycompany.myproject     -DappsFolderName=myproject     -DartifactName="My Project"     -DcqVersion="5.6.1"     -DpackageGroup="My Company" [INFO] Scanning for projects... Downloading: https://repo.adobe.com/nexus/content/groups/public/org/apache/maven/plugins/maven-metadata.xml Downloading: https://repo.adobe.com/nexus/content/groups/public/org/codehaus/mojo/maven-metadata.xml [WARNING] Could not transfer metadata org.apache.maven.plugins/maven-metadata.xml from/to adobe-public-releases (https://repo.adobe.com/nexus/content/groups/public): peer not authenticated [WARNING] Could not transfer metadata org.codehaus.mojo/maven-metadata.xml from/to adobe-public-releases (https://repo.adobe.com/nexus/content/groups/public): peer not authenticated Downloading: https://repo.adobe.com/nexus/content/groups/public/org/apache/maven/plugins/maven-archetype-plugin/maven-metadata.xml [WARNING] Could not transfer metadata org.apache.maven.plugins:maven-archetype-plugin/maven-metadata.xml from/to adobe-public-releases (https://repo.adobe.com/nexus/content/groups/public): peer not authenticated [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Maven Stub Project (No POM) 1 [INFO] ------------------------------------------------------------------------ [WARNING] Failure to transfer org.apache.maven.plugins/maven-metadata.xml from https://repo.adobe.com/nexus/content/groups/public was cached in the local repository, resolution will not be reattempted until the update interval of adobe-public-releases has elapsed or updates are forced. Original error: Could not transfer metadata org.apache.maven.plugins/maven-metadata.xml from/to adobe-public-releases (https://repo.adobe.com/nexus/content/groups/public): peer not authenticated [WARNING] Failure to transfer org.codehaus.mojo/maven-metadata.xml from https://repo.adobe.com/nexus/content/groups/public was cached in the local repository, resolution will not be reattempted until the update interval of adobe-public-releases has elapsed or updates are forced. Original error: Could not transfer metadata org.codehaus.mojo/maven-metadata.xml from/to adobe-public-releases (https://repo.adobe.com/nexus/content/groups/public): peer not authenticated [WARNING] Failure to transfer org.apache.maven.plugins:maven-archetype-plugin/maven-metadata.xml from https://repo.adobe.com/nexus/content/groups/public was cached in the local repository, resolution will not be reattempted until the update interval of adobe-public-releases has elapsed or updates are forced. Original error: Could not transfer metadata org.apache.maven.plugins:maven-archetype-plugin/maven-metadata.xml from/to adobe-public-releases (https://repo.adobe.com/nexus/content/groups/public): peer not authenticated [INFO] [INFO] >>> maven-archetype-plugin:2.3:generate (default-cli) @ standalone-pom >>> [INFO] [INFO] <<< maven-archetype-plugin:2.3:generate (default-cli) @ standalone-pom <<< [INFO] [INFO] --- maven-archetype-plugin:2.3:generate (default-cli) @ standalone-pom --- [INFO] Generating project in Interactive mode [INFO] Archetype defined by properties Downloading: http://repo.adobe.com/nexus/content/groups/public/com/day/jcr/vault/multimodule-content-package-archetype/1.0.2/multimodule-content-package-archetype-1.0.2.jar Downloading: https://repo.adobe.com/nexus/content/groups/public/com/day/jcr/vault/multimodule-content-package-archetype/1.0.2/multimodule-content-package-archetype-1.0.2.jar [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 3.412s [INFO] Finished at: Mon Apr 20 15:04:10 EDT 2015 [INFO] Final Memory: 11M/81M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:2.3:generate (default-cli) on project standalone-pom: The desired archetype does not exist (com.day.jcr.vault:multimodule-content-package-archetype:1.0.2) -> [Help 1] [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/MojoFailureException
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by smacdonald2008

What document are you following. I just tested this Maven AEM project listed in this community article:

https://helpx.adobe.com/experience-manager/using/creating-aem-project-using-intellij.html

The Maven command is:

mvn archetype:generate -DarchetypeRepository=http://repo.adobe.com/nexus/content/groups/public/ -DarchetypeGroupId=com.day.jcr.vault -DarchetypeArtifactId=multimodule-content-package-archetype -DarchetypeVersion=1.0.2 -DgroupId=com.aem.community -DartifactId=echoproject -Dversion=1.0-SNAPSHOT -Dpackage=com.aem.community -DappsFolderName=myproject -DartifactName="My Project" -DcqVersion="5.6.1" -DpackageGroup="My Company"

It works as expected. 

9 replies

smacdonald2008
smacdonald2008Accepted solution
Level 10
October 16, 2015

What document are you following. I just tested this Maven AEM project listed in this community article:

https://helpx.adobe.com/experience-manager/using/creating-aem-project-using-intellij.html

The Maven command is:

mvn archetype:generate -DarchetypeRepository=http://repo.adobe.com/nexus/content/groups/public/ -DarchetypeGroupId=com.day.jcr.vault -DarchetypeArtifactId=multimodule-content-package-archetype -DarchetypeVersion=1.0.2 -DgroupId=com.aem.community -DartifactId=echoproject -Dversion=1.0-SNAPSHOT -Dpackage=com.aem.community -DappsFolderName=myproject -DartifactName="My Project" -DcqVersion="5.6.1" -DpackageGroup="My Company"

It works as expected. 

jayproulx
jayproulxAuthor
Level 2
October 16, 2015

Thanks for the follow up Scott!

I’m following the docs here:  https://docs.adobe.com/docs/en/aem/6-0/develop/dev-tools/ht-projects-maven.html

 

 

It’s definitely something in my maven stack, if I wget the archetype dependency and copy it manually into .m2/repository it’ll work.  That’s obviously not sustainable for all affected dependencies.

The archetype itself is not my primary concern, it’s the error I’m getting (the "peer not authenticated” error) that affects my other builds that I’m trying to troubleshoot.

The latest things I’ve tried are importing the chain for the repo.adobe.com SSL cert into my cacerts keystone, with the same results.  I’ve also tried:

 -Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true

But that gives me a different error.

The only thing that I’ve got on this machine (new for development) is Maven 3.0.5, and the repo.adobe.com settings.xml.  I’ve never needed to go to such an extent to set up my development environment before which leads me to believe the problem is somewhere else.

jayproulx
jayproulxAuthor
Level 2
October 16, 2015

I upgraded to a JDK8 and the issue doesn't seem to reproduce...  I'm going to assume that the cert chain (somewhere in that cert chain) that was in the default OSX 1.6 JDK didn't align with the SSL cert for repo.adobe.com.

So, my issue is resolved, but it might be worth a quick pass over the docs.adobe.com content and make sure it still works with older JDK's...  especially now that 6.0 SP1 supports JDK8, you might need to bump the minimum JDK requirements for development...

RK30
RK30
January 25, 2016

I am also facing same problem and even upgrading to JDK 8 is not working for me. 

[INFO] Scanning for projects... Downloading: https://repo.adobe.com/nexus/content/groups/public/com/day/jcr/vault/content-package-maven-plugin/0.0.23/content-package-maven-plugin-0.0.23.pom [ERROR] [ERROR] Some problems were encountered while processing the POMs: [ERROR] Unresolveable build extension: Plugin com.day.jcr.vault:content-package-maven-plugin:0.0.23 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.23 @ [ERROR] Unknown packaging: content-package @ line 20, column 16 @ [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR]   The project com.test.sample:test.ui.apps:0.0.1-SNAPSHOT (/ms/.global/ny.w/user/i/ingoler.dev/shadow/test_aem/src/ui.apps/pom.xml) has 2 errors [ERROR]     Unresolveable build extension: Plugin com.day.jcr.vault:content-package-maven-plugin:0.0.23 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.23: Could not transfer artifact com.day.jcr.vault:content-package-maven-plugin:pom:0.0.23 from/to adobe-public-releases (https://repo.adobe.com/nexus/content/groups/public): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target -> [Help 2] [ERROR]     Unknown packaging: content-package @ line 20, column 16 [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/PluginManagerException
smacdonald2008
smacdonald2008
Level 10
January 25, 2016

Look at AEM docs 

PREREQUISITES

  • The Java Runtime Environment (JRE). Version 1.7 is preferred.
RK30
RK30
January 25, 2016

yes, we are still using 1.7 but after this error started appearing trying to fix these. Previously same build was working but all of a sudden started getting these errors.

RK30
RK30
January 25, 2016

Even if I try to go to 'http://cwiki.apache.org/confluence/display/MAVEN/PluginManagerException' ut says Page not found.

jayproulx
jayproulxAuthor
Level 2
January 25, 2016

@RK30, @smacdonald2008 I should have replied back here.  The problem is when you’re using OpenJDK, it’s missing certificates in the certificates chain that Nexus uses.  Use an official Oracle JDK release and you should be fine.  I can’t comment on JDK 1.7 (AEM 6 SP1+ recommends 1.8), but this has reproduced on all of our build machines.

RK30
RK30
January 25, 2016

@jayproulx that for your reply, we are using oraclejdk/1.7.0_80

Terms & ConditionsAccessibility statement

Loading footer...