1. 27 Jan, 2018 5 commits
  2. 18 Aug, 2017 1 commit
    • mevenson@1c010e3e-69d0-11dd-93a8-456734b0d56f's avatar
      abcl-asdf: fix for maven-3.5.0 · 0a0c21a9
      Various fixups in a hack 'n slash to get maven-3.5.0 working.
      
      From <https://maven.apache.org/docs/3.5.0/release-notes.html>:
      
          After Maven 3.3.9 was released, the Eclipse Aether project was
          retired and the code base was migrated to the Apache Maven
          project.
      
          The original goal for the 3.4.0 release was to replace Aether with
          the exact same code after migration to the Apache Maven project
          and then proceed with bug fixes to the resolver code as well as
          other areas of Maven.
      
          The migration of the code between the two foundations took longer
          than expected and as a result there were other changes committed
          to Maven core that were outside the scope of intent for 3.4.0.
      
          In order to refocus on the original intent for 3.4.0, the decision
          was taken to revert the Maven core history to the point of the
          3.3.9 release and merge in the desired changes one at a time.
      0a0c21a9
  3. 04 Jul, 2017 1 commit
  4. 13 Jun, 2017 1 commit
  5. 11 Jun, 2017 1 commit
  6. 25 May, 2017 3 commits
    • mevenson@1c010e3e-69d0-11dd-93a8-456734b0d56f's avatar
      asdf-mvn-module: fix test invocation · f7daf624
      Remove duplicate defintion of RESOLVE-MULTIPLE-MAVEN-DEPENDENCIES
      f7daf624
    • mevenson@1c010e3e-69d0-11dd-93a8-456734b0d56f's avatar
      asdf-mvn-module: enable use of MVN-MODULE in ASDF definitions · 53256660
      The MVN-MODULE component allows finer control over Maven's
      behavior when the transitive dependency graph contains conflicting
      requirements.
      
      (:mvn-module NAME
         :dependencies DEPENDENCIES
         :managed-dependencies MANAGED-DEPENDENCIES
         :exclusions EXCLUSIONS)
      
      where
      
      DEPENDENCIES
      
         A list of Maven artifacts in the form of colon or slash separated
         components GROUPID:ARTIFACTID:VERSIONID.
      
      MANAGED-DEPENDENCIES
      
         A List of maven artifacts. If an dependency with same GROUPID and
         ARTIFACTID are encountered, the version specified here overrides.
      
      EXCLUSIONS
      
         A list of partial maven artifacts groupid:artifactid. Dependencies
         with same groupid and artifactid are exluded
      
      
      An example of a MVN-MODULE ASDF declaration:
      
      (defsystem foo
        :defsystem-depends-on (asdf-mvn-module)
        :components ((:mvn-module maven
      		:dependencies
      		("net.sourceforge.owlapi/pellet-cli-ignazio1977/2.4.0-ignazio1977"
      		  "org.semanticweb.elk/elk-owlapi/0.4.3"
      		  "net.sourceforge.owlapi/org.semanticweb.hermit/1.3.8.413"
      		  "net.sourceforge.owlapi/owlapi-distribution/4.2.6"
      		  "net.sourceforge.owlapi/owlexplanation/2.0.0"
      		  "de.sciss/prefuse-core/1.0.1"
      		  "de.sciss/prefuse-demos/1.0.1")
      		:managed-dependencies
      		("org.slf4j/slf4j-api/1.7.21"
      		 "net.sourceforge.owlapi:owlapi-distribution:4.2.6")
      		:exclusions
      		("net.sourceforge.owlapi:owlapi-osgidistribution"
                       "edu.stanford.protege:org.protege.editor.owl")))
      
      c.f. <https://mailman.common-lisp.net/pipermail/armedbear-devel/2017-April/003810.html>
      
      Originally from <https://github.com/alanruttenberg/abcl/blob/stage/contrib/abcl-asdf/>.
      53256660
    • mevenson@1c010e3e-69d0-11dd-93a8-456734b0d56f's avatar
      Refactor out initialization pattern for Maven as WITH-AETHER to be · d53b9c7f
      used by external consumers/manipulators of the Maven Aether libraries.
      
      Unfinished, but can be used now to guarantee that ABCL-ASDF has
      located Maven, which will be retrofitted compatible with current
      usage.
      
      
      TODO Introduce toplevel handler for finding Maven.
      d53b9c7f
  7. 23 May, 2017 1 commit
    • mevenson@1c010e3e-69d0-11dd-93a8-456734b0d56f's avatar
      Move the failing test for maven dependencies into ABCL-ASDF · 53605b1c
      This test only makes sends if ABCL-ASDF can be loaded.
      
      Fixed 't/resolve-multiple-maven-dependencies.lisp' to running, but now
      failing on download of HeRMIT artifact:
      
           Java exception
           'org.eclipse.aether.resolution.DependencyResolutionException: The
           following artifacts could not be resolved:
           net.sourceforge.owlapi:org.semanticweb.hermit:jar:1.3.8.413,
           net.sourceforge.owlapi:owlapi-distribution:jar:4.2.6,
           net.sourceforge.owlapi:pellet-cli-ignazio1977:jar:2.4.0-ignazio1977,
           org.semanticweb.elk:elk-reasoner:jar:0.4.3,
           net.sourceforge.owlapi:owlexplanation:jar:2.0.0: Could not find
           artifact net.sourceforge.owlapi:org.semanticweb.hermit:jar:1.3.8.413'.
      53605b1c
  8. 22 May, 2017 1 commit
  9. 16 May, 2017 1 commit
  10. 27 Apr, 2017 1 commit
  11. 28 Mar, 2017 2 commits
  12. 02 Feb, 2017 3 commits
    • mevenson@1c010e3e-69d0-11dd-93a8-456734b0d56f's avatar
    • mevenson@1c010e3e-69d0-11dd-93a8-456734b0d56f's avatar
      Standardize use CL:*LOAD-VERBOSE* to control loading verbosity · 5992ced7
      Normalize logging output to a Lisp comment prefix (#\;) with a single tag
      that identifies the "subsystem" emitting the diagnostic.
      
      ABCL-ASDF:*MAVEN-VERBOSE* SYS:*ABCL-CONTRIB-VERBOSE* have been removed; use
      CL:*LOAD-VERBOSE* to control them.
      
      ASDF::*VERBOSE-OUT* and QUICKLISP-CLIENT::*QUICKLOAD-VERBOSE* cannot
      be easily modified while keeping in-sync with upstream, but they both
      seem to respect setting CL:*LOAD-VERBOSE* to nil to muffle output.
      
      EXT::*WARN-ON-REDEFINITION* signals conditions rather than just
      emitting error messages, so it has not been touched as theoretically
      some compiler tooling may be somehow be depending on its SIGNAL
      behavior.  As such, once an implementation that signals the same
      warnings as EXT::*WARN-ON-REDEFINITION* based on CL:*COMPILE-VERBOSE*
      setting should be maintained during a deprecation phase.
      
      ------------------------------------------------------------------------
      # From <https://github.com/armedbear/abcl/commit/6cc94a54cf9256b2a0f13857d4c448d3b5c044fc>
      
      ## Alan Ruttenberg
      
      Really this should just respect load-verbose. If you really want to
      fix this properly, do that. There are a proliferation of settings one
      has to know about if one wants ABCL to shut up while starting up, and
      any beginner will have a hell of a time accomplishing this. There
      ought to be a single variable that indicates you don't want these
      messages.
      
      - *load-verbose*
      - system::*verbose*
      - asdf::*verbose-out*
      - abcl-asdf::*maven-verbose
      - quicklisp-client::*quickload-verbose*
      - ext::*warn-on-redefinition*
      
      ## Mark Evenson
      
      Using CL:LOAD-VERBOSE to unify the control of all this logging
      behavior for ABCL is an excellent way forward here.
      
      This wouldn't help with quicklisp-client::quickload-verbose (not our code).
      
      An alternative would be to have some sort of "categorical logging
      system" (ala log4j) which would allow one to selectively enable
      classes of logging output ("show me all diagnostic from loading
      ABCL-CONTRIB"), but a basic boolean predicate here, unified into the
      standardized mechanism would go a long ways.
      
      ------------------------------------------------------------------------
      
      Originated with <https://github.com/armedbear/abcl/pull/37>.
      5992ced7
    • mevenson@1c010e3e-69d0-11dd-93a8-456734b0d56f's avatar
  13. 23 Jan, 2017 1 commit
    • 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
      JVM.
      
      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>.
      a5b536f7
  14. 26 Dec, 2016 1 commit
    • mevenson@1c010e3e-69d0-11dd-93a8-456734b0d56f's avatar
      abcl-asdf: fix problems with test suite's reliance on PROVE · cb70478c
      Even though defining our tests ASDF subcomponents are where we wish to
      eventually end up, currently there can be problems with referencing
      testing dependencies that are inadvertently tickled by their mere
      declaration.  To eliminate this possiblity, we move the test
      definitions to their own file, which should work as long as these
      definitions aren't referenced at runtime.
      cb70478c
  15. 13 Dec, 2016 1 commit
  16. 29 Nov, 2016 1 commit
  17. 21 Oct, 2016 1 commit
  18. 08 Oct, 2016 2 commits
  19. 28 Nov, 2015 1 commit
  20. 01 Jul, 2015 1 commit
  21. 30 Jun, 2015 3 commits
  22. 19 Apr, 2015 2 commits
  23. 10 Jan, 2015 1 commit
  24. 07 Jan, 2015 1 commit
  25. 05 Jan, 2015 3 commits