[Armedbear-ticket] [armedbear] #360: Unable to load hunchentoot via quicklisp (maven, asdf problem?)

[armedbear]

#360: Unable to load hunchentoot via quicklisp (maven, asdf problem?)
-----------------------------+----------------------
  Reporter:  david creelman  |      Owner:  mevenson
      Type:  defect          |     Status:  accepted
  Priority:  major           |  Milestone:
 Component:  other           |    Version:
Resolution:                  |   Keywords:
-----------------------------+----------------------

Comment (by mevenson):

 Closing ticket as the original poster never replied with additional
 details, and the conversation with Alan contains a lot of additional
 information.  The intention is to link additional tickets here to follow
 up upon to resolve issues using the Maven connector.

 To summarize:

 1.  Both Drakma and Hunchentoot use cl+ssl to interact with OpenSSL
 libraries via CFFI.

 2. One may instruct Drakma or Hunchentoot to load without SSL by pushing
 the appropriate symbol to *FEATURES*, namely by

 {{{
    (push :drakma-no-ssl *features*)
 }}}

 or

 {{{
    (push :hunchentoot-no-ssl *features*)
 }}}

 respectively.  Requesting Drakma/Hunchentoot not to use SSL in this manner
 is probably best done in the ABCL startup file at <file:~/.abclrc>.

 3.  For CFFI, ABCL uses the Java JNA library.  The JNA library is located
 over the network and loaded by the ABCL-ASDF Maven connector, which
 requires Maven to be installed locally.  [ticket:363 The error message for
 not finding Maven needs to be more informative].

 4.  If the heuristic for finding the Maven jar archives fails, but Maven
 is installed locally, one may explicitly specify this location by setting
 the special ABCL-ASDF::*MVN-LIBS-LOCATION*.  The ABCL-ASDF Maven component
 does not use the Maven 'mvn' command directly, but instead uses the
 location of the 'mvn' command on the filesystem in an attempt to locate
 and load the Maven jar archives for direct manipulation of the Aether
 connector.  When this heuristic fails, the [ticket:378 ABCL-ASDF:*MVN-
 LIBS-DIRECTORY*] needs to be specified explicitly.

 5.  There should be some facility to print diagnostics on what the current
 state of a given ABCL process with Maven in a user friendly manner.

--
Ticket URL: <http://abcl.org/trac/ticket/360#comment:21>
armedbear <http://abcl.org>
armedbear