Opened 9 years ago
Closed 8 years ago
#390 closed defect (fixed)
ABCL-ASDF:RESOLVE not working
Reported by: | Mark Evenson | Owned by: | |
---|---|---|---|
Priority: | critical | Milestone: | 1.4.0 |
Component: | abcl-contrib | Version: | 1.4.0-dev |
Keywords: | abcl-asdf | Cc: | |
Parent Tickets: |
Description
Without the presence of a <file:~/.m2/> directory, populated by command line mvn usage, the ABCL-ASDF mechanism is not working:
CL-USER> (ABCL-ASDF:RESOLVE-DEPENDENCIES "net.java.dev.jna" "jna" :VERSION "4.1.0")
Java exception 'org.eclipse.aether.collection.DependencyCollectionException: Failed to read artifact descriptor for net.java.dev.jna:jna:jar:4.1.0'. [Condition of type JAVA-EXCEPTION] Restarts: 0: [RETRY] Retry compiling #<ASDF/INTERFACE:MVN "jna" "net.java.dev.jna/jna/4.1.0">. 1: [ACCEPT] Continue, treating compiling #<ASDF/INTERFACE:MVN "jna" "net.java.dev.jna/jna/4.1.0"> as having been successful. 2: [RETRY] Retry ASDF operation. 3: [CLEAR-CONFIGURATION-AND-RETRY] Retry ASDF operation after resetting the configuration. 4: [RETRY] Retry SLIME REPL evaluation request. 5: [*ABORT] Return to SLIME's top level.
Switching between Maven versions 3.2.5 and 3.3.3 seems to give the same problems.
Attachments (1)
Change History (8)
comment:1 Changed 9 years ago by
comment:2 Changed 9 years ago by
WORKAROUND: ensure that you use maven-3.2.3 from the environment.
Verify via ENSURE-MVN-VERSION
CL-USER> (abcl-asdf:ensure-mvn-version) T (3 2 3)
I believe (but have not verified) that the patches from Cyrus to enable maven-3.2.5 or later just never checked whether the artifacts were already present locally in the <file:~/.m2/> Maven cache.
Documentation on using Aether apart from Maven has gotten better.
comment:3 Changed 9 years ago by
An example with transitive dependencies:
(abcl-asdf:Resolve "org.bitcoinj:bitcoinj-core:0.12.3")
comment:5 Changed 9 years ago by
Resolution: | fixed |
---|---|
Status: | closed → reopened |
(lisp-implementation-version) "1.4.0-dev" "OpenJDK_64-Bit_Server_VM-Oracle_Corporation-1.8.0_45-b14" "amd64-FreeBSD-10.1-RELEASE" ABCL-ASDF> (abcl-asdf:ensure-mvn-version) T (3 1 1)
comment:7 Changed 8 years ago by
Milestone: | 1.5.0 → 1.4.0 |
---|---|
Resolution: | → fixed |
Status: | reopened → closed |
CL-USER> (ABCL-ASDF:RESOLVE-DEPENDENCIES "net.java.dev.jna" "jna" :VERSION "4.1.0") ARTIFACT_RESOLVING net.java.dev.jna:jna:pom:4.1.0 ARTIFACT_RESOLVED net.java.dev.jna:jna:pom:4.1.0 (/Users/evenson/.m2/repository/net/java/dev/jna/jna/4.1.0/jna-4.1.0.pom) @ /Users/evenson/.m2/repository (enhanced) ARTIFACT_RESOLVING net.java.dev.jna:jna:jar:4.1.0 ARTIFACT_RESOLVED net.java.dev.jna:jna:jar:4.1.0 (/Users/evenson/.m2/repository/net/java/dev/jna/jna/4.1.0/jna-4.1.0.jar) @ /Users/evenson/.m2/repository (enhanced) "/Users/evenson/.m2/repository/net/java/dev/jna/jna/4.1.0/jna-4.1.0.jar" CL-USER> (lisp-implementation-version) "1.5.0-dev" "Java_HotSpot(TM)_64-Bit_Server_VM-Oracle_Corporation-1.8.0_112-b16" "x86_64-Mac_OS_X-10.12.1"
As a workaround, one may install artifacts by hand via the mvn command line.
The following will pull the artifacts required to get the depdendencies needed by CFFI