Hi Erik,
>From what I understand, to close a classloader, you would need to also
remove all references to it or set the references to it to nil/null.
In the case of an eval in the repl, again I'm assuming we do lose that
reference once we are out of the scope of the eval.
While I said not reloadi
On 25 Mai, 08:03, Brent Millare wrote:
> Erik, what you said seems to make sense. So the question now is, since
> a new classloader is started during each eval at the repl, does that
> mean that it is closed after each repl statement? This seems to be the
> case because after requiring a namespa
Erik, what you said seems to make sense. So the question now is, since
a new classloader is started during each eval at the repl, does that
mean that it is closed after each repl statement? This seems to be the
case because after requiring a namespace in a previous command at the
repl, I can no lon
Classloaders are generally additive. The system classloader pulls in
standard Java libraries and anything else you specify on the command
line. Then you can add classloaders, and they delegate back to the
parent classloader as a default behavior. When you want to get rid of
the JAR references fo
I am creating another dependency management system that using dynamic
compilation to load dependencies during runtime. My actual issue is I
needed to reconstruct the new effective classpath which should include
the classpath given (from (System/getProperty "java.class.path")) at
the commandline and
Hi,
I guess clojure creates a new classloader for each eval to make
redefining deftypes possible.
Is your requirement somehow related to applets or webstart or other
sandboxes environments?
> I need a reliable method to provide enforce usage of a single
> classloader for an entire session, this a
