Last change
on this file was
13550,
checked in by Mark Evenson, 13 years ago
|
Maven dependencies loaded via ASDF defintions.
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.
|
File size:
265 bytes
|
Line | |
---|
1 | (defpackage #:abcl-asdf |
---|
2 | (:use :cl) |
---|
3 | (:export |
---|
4 | #:satisfy |
---|
5 | #:as-classpath |
---|
6 | |
---|
7 | #:resolve-artifact |
---|
8 | #:resolve-dependencies |
---|
9 | |
---|
10 | #:add-directory-jars-to-class-path |
---|
11 | #:need-to-add-directory-jar? |
---|
12 | |
---|
13 | #:*added-to-classpath* |
---|
14 | #:*inhibit-add-to-classpath*)) |
---|
15 | |
---|
Note: See
TracBrowser
for help on using the repository browser.