- 05 Jan, 2015 1 commit
-
-
- 19 Aug, 2014 1 commit
-
-
- 27 Apr, 2014 1 commit
-
-
From a patch for OpenBSD provided by Timo Myyrä.
-
- 27 Jan, 2014 1 commit
-
-
- 16 Aug, 2013 1 commit
-
-
Big thanks to Anton Vodonosov for the initial patch. The code in maven-embedder.lisp should now work for all versions of Maven greater than 3.0.3. Added MAKE-ARTIFACT and MAKE-ARTIFACT-REQUEST for creating the correponding Aether objects.
-
- 13 Jun, 2013 1 commit
-
-
- 21 May, 2013 1 commit
-
-
Returns the found (MAJOR MINOR PATCH) as the second value. Adding support for test framework (use :RT).
-
- 06 Dec, 2012 1 commit
-
-
doc: Start annotating all the places we need to change things with RDF. Do TODO: grovel through the source tree to find all textual lines containing probable RDF statements.
-
- 28 Nov, 2012 1 commit
-
-
Warn when interpreting alias for "com.sun.jna:jna". Closes #268.
-
- 10 Nov, 2012 1 commit
-
-
DEFSYSTEM-DEPENDS-ON loads its requirements before the system definition is evaluated which is not needed in this case. The abcl-test-lisp ASDF definition is contained in the toplevel "abcl.asdf" file, which I usually have symlinked into ~/.asdf-install-dir/systems/ for convenience.
-
- 09 Nov, 2012 2 commits
-
-
An ASDF:MVN component can now optionally specify a CLASSNAME that if able to be found in the current jvm process, inhbits further loading from the network. An ASDF:MVN component may also optionally specify an ALTERNATE-URI that will be added to the current jvm classpath if Maven cannot be invoked. Most jvm implementations won't access such jar archives from the network by default, so this is an intermediate step before actually writing the code to download the jar to the local filesystem to then be added. Refresh documentation in README.markdown.
-
Further work needed as something more meaningful should be returned other than "The value NIL is not of type REAL" when abcl-asdf can't parse the Maven version string. Initial patch by Christoph.
-
- 13 Oct, 2012 1 commit
-
-
Bump version to indicate that we have greater faith of the stability of the interface. N.b. seems to break [Jeannie](http://bitbucket.org/easye/jeannie/).
-
- 12 Oct, 2012 1 commit
-
-
- 08 Oct, 2012 1 commit
-
-
CL:REQUIRE now calls PROVIDE with module names when successful (as opposed to relying in the loaded code to do this explicity).
-
- 01 Apr, 2012 1 commit
-
-
The ASDF:MVN component now gets an ASDF:REPOSITORY slot to be populated with the Aether repository to pass.
-
- 06 Feb, 2012 1 commit
-
-
This aligns the function to the underlying Maven Aether API. As far as I can tell, nothing was using RESOLVE-ARTIFACT anyways.
-
- 01 Feb, 2012 1 commit
-
-
Increment abcl-asdf ASDF version to 0.6.0 to denote the ability to specify an http proxy for Maven.
-
- 25 Jan, 2012 4 commits
-
-
The system defintion ABCL-ASDF-TEST now loads again. Use ABCL-ASDF-TEST:RUN as the executable symbol for manual tests.
-
Start separating out the public api by exporting and documenting symbols.
-
-
Part of the process of cleaning up ABCL-ASDF to work with more Maven versions. Seems to be failing for OS X Maven 3.0.4, so need to do a round of testing. Add system definition of ABCL-ASDF-TEST which becomes the behavior for invoking ASDF:TEST-SYSTEM on ABCL-ASDF. Really update to version "0.5.0". Correct misspellings. TODO: figure out a list of repos to iteratively search. TODO: overload the system defintion version mechanism to allow non-integer values, or just use the IRI class? TODO: be more verbose on searching/downloading Maven artifacts as it can be quite slow for large amounts of artifacts.
-
- 06 Sep, 2011 1 commit
-
-
Document functions a bit better. Include an example that can be used without reference to ASDF.
-
- 30 Aug, 2011 1 commit
-
-
If a Maven3 installation can be found via FIND-MVN, ASDF definitions of the form (:mvn "GROUP-ID/ARTIFACT-ID" :version "VERSION") will be resolved at the ASDF system load time via the Maven Aether resolution mechanism. The log4j example wrapping now works. N.b. this code seriously distorts some of the notions of ASDF which really seems to depend on its components actually being resident on the filesystem. This needs to be adressed ("blessed") via consultation with ASDF developers to ensure that the path we are choosing is reasonably future-proof.
-
- 01 Aug, 2011 3 commits
-
-
The use of this variable is perhaps slightly obsolescent with the use of JAVA:DUMP-CLASSPATH, but provides a convenient shortcut to quickly find out what has been added by JAVA:ADD-TO-CLASSPATH.
-
This increases compatibility with the original version of JSS. The only possible situation where this doesn't make sense would be if a jar where to end in something other than ".jar", like perhaps ".zip" or ".war". In this case, additional ASDF classes should be defined extending JAR-FILE.
-
The JAR-FILE, JAR-DIRECTORY, and CLASS-FILE-DIRECTORY ASDF extensions are now part of the ABCL-ASDF contrib as we aim to centralize all such things in one place. *ADDED-TO-CLASSPATH* is now part of the ABCL-ASDF package as well. There is currently a (mostly) recursive relationship between JSS and ABCL-ASDF, as each (mostly) requires the other for operation. JSS:ENSURE-COMPATIBILITY will ensure that JSS continues to understand the refactored extensions.
-
- 21 Jun, 2011 2 commits
-
-
I don't think the download portion is quite working yet.
-
-
- 17 Jun, 2011 1 commit
-
-
- 30 May, 2011 1 commit
-
-
The recursive dependencies are just recorded, not packaged.
-