14 Mar
2010
14 Mar
'10
2:36 p.m.
On 3/12/10 6:30 PM, Alan Ruttenberg wrote:
[…]
Here's the start of the code for managing the jars. http://svn.mumble.net:8080/svn/lsw/trunk/util/jar-current-classpath.lisp
The problem occurred when I tried to load the compiled system code so prepared.
I implemented the use of :ABSOLUTE directory components for jar pathnames in [r12531][1], which worked in your described scenario as I was able to replicate it from your description (impressive function JAR-CURRENT-CLASSPATH!)
If this implmentation does not suit your needs, please let me know.
[1]: http://trac.common-lisp.net/armedbear/changeset/12531
--
"A screaming comes across the sky. It has happened before, but there
is nothing to compare to it now."