Page MenuHomePhabricator

Apache atlas build fails due to expired certificate (https://maven.restlet.com)
Closed, ResolvedPublic

Description

Running the Apache Atlas build instructions fails at the following step: mvn clean -DskipTests package, due to an invalid certificate:

[ERROR] Failed to execute goal on project atlas-testtools: Could not resolve dependencies for project org.apache.atlas:atlas-testtools:jar:2.2.0: Failed to collect dependencies at org.apache.solr:solr-test-framework:jar:8.6.3 -> org.restlet.jee:org.restlet:jar
:2.4.3: Failed to read artifact descriptor for org.restlet.jee:org.restlet:jar:2.4.3: Could not transfer artifact org.restlet.jee:
org.restlet:pom:2.4.3 from/to maven-restlet (https://maven.restlet.com): sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed: NotAfter: Sat Dec 11 22:28:29 UTC 2021 -> [Help 1]

I reported this and another issue at user@atlas.apache.org, and have yet to hear back. I also attempted to reach out to the organization that mantains maven.restlet.com, Talend, but have yet to hear back. I appears they migrated their maven repository to maven.restlet.talend.com, which maven.restlet.com would redirect to if the ssl expiration warning is ignored.

One workaround is to disable ssl entirely as follows:

mvn clean -DskipTests
-Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true
-Dmaven.wagon.http.ssl.ignore.validity.dates=true install

But this is a bad idea this could run malicious code.

Event Timeline

You might be able to workaround this by manually downloading and then uploading this dependency to our archiva, and then making sure your own maven repo settings.xml is configured to use our archiva.

@razzi I suggest to file a pull request (if you have a fix) and ask a feedback in their dev@ mailing list, it is easy that the user@ is not watched a lot by devs.

You might be able to workaround this by manually downloading and then uploading this dependency to our archiva, and then making sure your own maven repo settings.xml is configured to use our archiva.

+1 on the suggestion

I believe that this has now been fixed by a third-party. Attempting to confirm now with a new build.

Confirmed with a fresh build and package.

I also got the build to work at one point, and we're pausing on Atlas due to the hive incompatibility.