Unable to build mockito due to PKIX error

8 views
Skip to first unread message

Jason Mathison

unread,
Jun 21, 2024, 1:25:35 PM (13 days ago) Jun 21
to mockito
Attempting to build the project is resulting in this error:


* What went wrong:
Could not resolve all files for configuration 'classpath'.
> Could not resolve com.gradle:gradle-enterprise-gradle-plugin:3.17.5.
Required by:
unspecified:unspecified:unspecified > com.gradle.enterprise:com.gradle.enterprise.gradle.plugin:3.17.5
> Could not resolve com.gradle:gradle-enterprise-gradle-plugin:3.17.5.
> Could not get resource 'https://plugins.gradle.org/m2/com/gradle/gradle-enterprise-gradle-plugin/3.17.5/gradle-enterprise-gradle-plugin-3.17.5.pom'.
> Could not GET 'https://plugins-artifacts.gradle.org/com.gradle/gradle-enterprise-gradle-plugin/3.17.5/ceaba883b0b5fd680881d83acf3a83a1f9563c79a7bb09e2b2981ca290b86d5a/gradle-enterprise-gradle-plugin-3.17.5.pom'.

> PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

> Could not resolve org.gradle.toolchains:foojay-resolver:0.8.0.

Required by:

unspecified:unspecified:unspecified > org.gradle.toolchains.foojay-resolver-convention:org.gradle.toolchains.foojay-resolver-convention.gradle.plugin:0.8.0

> Could not resolve org.gradle.toolchains:foojay-resolver:0.8.0.

> Could not get resource 'https://plugins.gradle.org/m2/org/gradle/toolchains/foojay-resolver/0.8.0/foojay-resolver-0.8.0.pom'.

> Could not GET 'https://plugins-artifacts.gradle.org/org.gradle.toolchains/foojay-resolver/0.8.0/a71672acad0c0aee39efa5753f5c94f9a4a35a1dac065e228bcac342dea7c548/foojay-resolver-0.8.0.pom'.

> PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target


I played with this for a while and couldn't figure out why Java is unhappy with the certificate.  I can download the noted file with Chrome. I am on the latest version of Java 17. Trying to use the mavenCentral() repository didn't work any better.

--Jason

Reply all
Reply to author
Forward
0 new messages