#268: ABCL-ASDF working with maven-3.0.3 ------------------------------------------+--------------------------------- Reporter: mevenson | Owner: mevenson Type: defect | Status: new Priority: blocker | Milestone: 1.1.0 Component: libraries | Version: Keywords: maven abcl-asdf abcl-contrib | ------------------------------------------+--------------------------------- OS X comes with maven-3.0.3 installed.
OSX Workaround: Use MacPorts to install maven3.
TODO: add an option upstream (+ffi) to pull in proper runtime dependency.
#268: ABCL-ASDF working with maven-3.0.3 ------------------------------------------+--------------------------------- Reporter: mevenson | Owner: mevenson Type: defect | Status: new Priority: blocker | Milestone: 1.1.0 Component: libraries | Version: Keywords: maven abcl-asdf abcl-contrib | ------------------------------------------+---------------------------------
Comment(by mevenson):
This used to work, which I tried to preserve by a method dispatch indirection. Need to figure out how to fix any remaining difference between that and the current use of Aether.
Background: maven-3.0.3 ships with a substantially different Aether connector. In the previous version, one *couldn't* successfully "steer" the Aether core code without using private methods. TODO: fallback to that "dirty" strategy via introspection of runtime failure.
#268: ABCL-ASDF working with maven-3.0.3 ------------------------+--------------------------------------------------- Reporter: mevenson | Owner: mevenson Type: defect | Status: closed Priority: blocker | Milestone: 1.1.0 Component: libraries | Version: Resolution: fixed | Keywords: maven abcl-asdf abcl-contrib ------------------------+--------------------------------------------------- Changes (by mevenson):
* status: new => closed * resolution: => fixed
Comment:
(In [14259]) abcl-asdf: restore the ability to use maven-3.0.3
Warn when interpreting alias for "com.sun.jna:jna".
Closes #268.
armedbear-ticket@common-lisp.net
-
armedbear