1. 21 Mar, 2014 1 commit
  2. 26 Jan, 2014 1 commit
  3. 25 Jan, 2014 1 commit
  4. 18 Dec, 2012 1 commit
  5. 06 Dec, 2012 1 commit
  6. 07 Nov, 2012 1 commit
  7. 08 Aug, 2012 1 commit
  8. 09 Jan, 2012 1 commit
    • mevenson@1c010e3e-69d0-11dd-93a8-456734b0d56f's avatar
      Fix #177: make logic for finding abcl-contrib more robust. · 2d523f72
      Issuing a (REQUIRE 'ABCL-CONTRIB) will now use the full name of the
      jar archive ABCL was loaded from if it is of the form `abcl.jar' or
      `abcl-x.y.z.jar` or `abcl-x.y.z-some-arbitrary-string.jar' to
      determine the location of the jar containing the ABCL-CONTRIB
      packages.  The namestrings of the ASDF systems located by this
      mechanism are now printed to *STANDARD-OUTPUT*.
      Installations of the implementations loading from non-standard
      locations may use the SYS::*ABCL-JAR* and SYS:*ABCL-CONTRIB* specials
      to override this behavior.
  9. 24 Oct, 2011 1 commit
  10. 27 May, 2011 1 commit
    • mevenson@1c010e3e-69d0-11dd-93a8-456734b0d56f's avatar
      Automagically find contrib via (REQUIRE :ABCL-CONTRIB). · badf8444
      REQUIREing :ABCL-CONTRIB will look for a 'abcl-contrib.jar' in the
      same directory as 'abcl.jar'.  If found, all the ASDF definitions one
      level deep will be added to the ASDF search path, allowing contribs to
      be loaded via REQUIRE or ASDF:LOAD-SYSTEM.
      No longer compile contribs as ASDF will do this for us.  Since we
      moved to ASDF2, the contrib FASLs have been compiled but not packaged,
      so this doesn't change any behavior except making packaging shorter.
      When we figure out how to package FASLs with ASDF systems in jar
      files, we will revisit this topic.