Project built with AEM Archetype 22 Fails to build - Failed to collect dependencies at io.wcm:io.wcm.testing.aem-mock.junit5:jar:2.5.2 | Community
Skip to main content
surenk
Level 4
January 7, 2020
Solved

Project built with AEM Archetype 22 Fails to build - Failed to collect dependencies at io.wcm:io.wcm.testing.aem-mock.junit5:jar:2.5.2

  • January 7, 2020
  • 3 replies
  • 4236 views

Built a new codebase using AEM Archetype 22. But code build (using command mvn clean install -PautoInstallPackage ) fails with the below message. How can this be resolved?

Trying to deploy to AEM 6.3.3 on Windows 10 Enterprise

[ERROR] Failed to execute goal on project sow3pocs.core: Could not resolve dependencies for project com.creditonebank.aem.pocs:sow3pocs.core:jar:1.0-SNAPSHOT: Failed to collect dependencies at io.wcm:io.wcm.testing.aem-mock.junit5:jar:2.5.2 -> io.wcm:io.wcm.testing.aem-mock.core:jar:2.5.2 -> com.day.commons:day-commons-gfx:jar:2.1.28: Failed to read artifact descriptor for com.day.commons:day-commons-gfx:jar:2.1.28: Could not transfer artifact com.day.commons:day-commons-gfx:pom:2.1.28 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 1]

 

Copy of `settings.xml` under .m2 folder is

<settings xmlns="https://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="https://maven.apache.org/SETTINGS/1.0.0 https://maven.apache.org/xsd/settings-1.0.0.xsd"> <profiles> <!-- ====================================================== --> <!-- A D O B E P U B L I C P R O F I L E --> <!-- ====================================================== --> <profile> <id>adobe-public</id> <activation> <activeByDefault>true</activeByDefault> </activation> <properties> <releaseRepository-Id>adobe-public-releases</releaseRepository-Id> <releaseRepository-Name>Adobe Public Releases</releaseRepository-Name> <releaseRepository-URL>https://repo.adobe.com/nexus/content/groups/public</releaseRepository-URL> </properties> <repositories> <repository> <id>adobe-public-releases</id> <name>Adobe Public Repository</name> <url>https://repo.adobe.com/nexus/content/groups/public</url> <releases> <enabled>true</enabled> <updatePolicy>never</updatePolicy> </releases> <snapshots> <enabled>false</enabled> </snapshots> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>adobe-public-releases</id> <name>Adobe Public Repository</name> <url>https://repo.adobe.com/nexus/content/groups/public</url> <releases> <enabled>true</enabled> <updatePolicy>never</updatePolicy> </releases> <snapshots> <enabled>false</enabled> </snapshots> </pluginRepository> </pluginRepositories> </profile> </profiles> <activeProfiles> <activeProfile>adobe-public</activeProfile> </activeProfiles> </settings>

 

 

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 arunpatidar

You can use the http adobe repository instead of https in setting.xml like this

<url>http://repo.adobe.com/nexus/content/groups/public/</url>

3 replies

Adobe Employee
January 7, 2020

Can you check if you are using the correct version of uber jar?

 

[1] https://repo.adobe.com/nexus/content/groups/public/com/adobe/aem/uber-jar/6.3.3.3/

surenk
surenkAuthor
Level 4
January 8, 2020
Thanks. Updating the uber jar from 6.5 to 6.3.3 helped to resolve. There were some missing dependencies, that i downloaded and copied manually to .m2/repository..
preetham_messi
New Member
February 1, 2024

Hey bud..! could you please share the changes you had made, i've been getting the same error.

 

Adobe Employee
January 7, 2020

This message here : 

Could not transfer artifact com.day.commons:day-commons-gfx:pom:2.1.28 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

 

Implies that you cannot establish a trusted SSL connection with the Nexus / Artifactory repository. 

arunpatidar
Community Advisor
arunpatidarCommunity AdvisorAccepted solution
Community Advisor
January 7, 2020

You can use the http adobe repository instead of https in setting.xml like this

<url>http://repo.adobe.com/nexus/content/groups/public/</url>

Arun Patidar