On Jan 4, 12:59 pm, "Stephen C. Gilardi" wrote:
> In my case, I set the value of java.ext.dirs to a list of just one
> directory. That directory contains (relative) symbolic links to all
> the Jar files and directories I want Clojure to use as its Classpath.
Symlinks! Ack! Terrible visions of
Stephen C. Gilardi wrote:
> The "java.ext.dirs" System property provides a very convenient way to
> set up and maintain a Classpath for Clojure REPLs.
[...]
> In my case, I set the value of java.ext.dirs to a list of just one
> directory. That directory contains (relative) symbolic links to all
On Jan 4, 6:06 pm, lpetit wrote:
> Note that since JDK 1.6, it is possible to use the * wildcard in
> classpath items to embed all the jars in a directory at once.
>
> So with proper use of links in a "root" directory containing a bunch
> of jars, it's possible to shorten the classpath to DIR/*
I think this should be fine for 99% of situations, but I think it's
also fair to say this is an unorthodox use of java.ext.dirs. I've
never really had a firm grip on the idiomatic use of Java's extension
mechanism, but I do know that they claim it is for well-established
extension/optional packag
Note that since JDK 1.6, it is possible to use the * wildcard in
classpath items to embed all the jars in a directory at once.
So with proper use of links in a "root" directory containing a bunch
of jars, it's possible to shorten the classpath to DIR/*:classes:src
BTW, java.ext.dirs' semantics i
The "java.ext.dirs" System property provides a very convenient way to
set up and maintain a Classpath for Clojure REPLs. The property can be
set from the command line used to launch Clojure (typically within a
launcher script). Its value is a list of directories whose *contents*
will be the
