Re: Could not transfer artifact net.java.dev.jna:jna:pom:5.5.0 from/to central (http://repo1.maven.org/maven2/): Transfer failed for http://repo1.maven.org/maven2/net/java/dev/jna/jna/5.5.0/jna-5.5.0.pom 501 HTTPS Required
Mark Evenson <[email protected]> Sat, 14 Mar 2020 13:06:41 +0100
| Newsgroups | gmane.editors.j.devel |
|---|---|
| Message-ID | <[email protected]> |
> On Mar 13, 2020, at 11:53, Anton Vodonosov <[email protected]> wrote: > > The following error started to happen recently (in my case in Travis CI runs of a library, which includes ABCL as one of the lisps): > > > jnaASDF could not load because Java exception 'org.eclipse.aether.collection.DependencyCollectionException: Failed to read artifact descriptor for net.java.dev.jna:jna:jar:5.5.0'.. > > Could not transfer artifact net.java.dev.jna:jna:pom:5.5.0 from/to central (http://repo1.maven.org/maven2/): Transfer failed for http://repo1.maven.org/maven2/net/java/dev/jna/jna/5.5.0/jna-5.5.0.pom 501 HTTPS Required > > > It must be caused by the following change in the maven central repo: > https://support.sonatype.com/hc/en-us/articles/360041287334-Central-501-HTTPS-Required > > What is the best way to solve this? > In other words, how to make sure ABCL uses the HTTPS versions of the > central repo URLs? > > Best regards, > - Anton As noted in <https://mailman.common-lisp.net/pipermail/armedbear-devel/2020-February/004035.html>, this has been fixed in the upcoming abcl-1.6.1 release. Placing the following stanza in <file:~/.abclrc> should fix the problem for existing installations of ACBL: (progn (require :abcl-contrib) (asdf:load-system :abcl-asdf) (setf (symbol-value (uiop:find-symbol* :*default-repository* :abcl-asdf)) "https://repo1.maven.org/maven2/"))) yers in CONS, Mark -- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now."