1. 29 May, 2017 2 commits
  2. 25 May, 2017 4 commits
  3. 23 May, 2017 5 commits
  4. 22 May, 2017 2 commits
    • mevenson@1c010e3e-69d0-11dd-93a8-456734b0d56f's avatar
      abcl-asdf: preparation to use utility functions from ABCL-BUILD · 96a17daa
      Import SPLIT-STRING for compatibility to its usage in ABCL-ASDF.
    • mevenson@1c010e3e-69d0-11dd-93a8-456734b0d56f's avatar
      Rework ABCL-BUILD as a contrib · f8592464
      ABCL-BUILD now more usefully installs necessary build machinery.
      Refactor the ABCL-BUILD Lisp based build to use use Ant, which allows
      us to canonicalize the build instructions in a much more configurable
      manner, restoring the cross-implementation build of ABCL for CL users
      who really do want to know about Java tooling.
      Since we want to use ASDF/UIOP anyways, this code is best expressed as
      an abcl contrib where such behavior can profitably take place.
      TODO: does not pass all tests
      TODO: API compatibility so that build-from-lisp.bash works
      TODO: If an invocable Ant cannot be found, then offer to install one via restart
      TODO: work backwards to the scenario that we are booting in pure
      interepreted mode without access to compilers.
  5. 16 May, 2017 1 commit
  6. 15 May, 2017 2 commits
  7. 27 Apr, 2017 1 commit
  8. 16 Apr, 2017 1 commit
  9. 28 Mar, 2017 2 commits
  10. 02 Feb, 2017 4 commits
  11. 01 Feb, 2017 2 commits
  12. 23 Jan, 2017 2 commits
    • mevenson@1c010e3e-69d0-11dd-93a8-456734b0d56f's avatar
      abcl-asdf: introduce JDK-JAR object to describe JDK tags (Alan Ruttenberg) · a5b536f7
      We introduce an ASDF component JDK-JAR, a jar file where the pathname
      and name are relative to the 'java.home' property of the executing
      Note that the use of JDK-JAR consistutes an experimental interface
      with a lot of potential problems going forward.  We note some of those
      issues for further consideration:
      1) Java9 does away with the packaging of system tools in jar files,
      using the Java module system to provide "optimized" access to system
      resources.  Therefore, a better abstraction would be to somehow
      describe the artifacts that need to be loaded to satisfy the
      dependencies, and then provide mappings to strategies that locate and
      load them within the JDK filesystem.  c.f. <http://abcl.org/trac/ticket/423>.
      2) The structure of the 'java.home' directory varies in unknown ways
      between JDK versions and across platforms, making the use of JDK-JAR
      relative pathnames need special casing for various situations.
      3) ABCL may be run on a JRE runtimes which have a different directory
      structure than a JDK, most notably missing the 'tools.jar' artifact.
      4) Given the problems arising from points 3 and 4, meaningful
      conditions and appropiate restarts should be emitted by ABCL-ASDF when
      it cannot satisfy JDK-JAR dependencies.  This machinery should also be
      extended to the other major current deficiency in ABCL-ASDF lack of
      intellible errors/meaningful restarts when Maven cannot be located.
      Despite these problems, it is more useful to experiment with being
      able to reference JDK artifacts in ABCL-ASDF definitions than not, so
      we include JDK-JAR as an experimental feature.
      We need some way to mark the JDK-JAR feature as experimental.  The
      easiest way forward would be to split it off into a separate file
      compilation unit with appropiate comments.
      Merges <https://github.com/armedbear/abcl/pull/35/files>.
    • mevenson@1c010e3e-69d0-11dd-93a8-456734b0d56f's avatar
      abcl-introspect: further fixes for stacktrace (Alan Ruttenberg) · 0947a4e8
      Fixes another attempt at accessing package name of nonexistent
      Merges <https://github.com/armedbear/abcl/pull/34>.
  13. 22 Jan, 2017 2 commits
  14. 20 Jan, 2017 1 commit
  15. 18 Jan, 2017 1 commit
  16. 16 Jan, 2017 4 commits
  17. 12 Jan, 2017 1 commit
  18. 08 Jan, 2017 1 commit
  19. 28 Dec, 2016 2 commits