REPL test classpaths

[Chas Emerick]

It looks like the REPL is currently being started with only the
"compile" library and build classpaths (and looking around in the
enclojure source seems to confirm that). That obviously makes it
impossible to refer to classes in test source directories or to load
clojure files that require or use clojure files that are in a test
source directory.

Changing this appears to be relatively easy, but I hesitate to submit
a patch to ensure that the REPL classpath consist of a union of the
compile and test classpaths in netbeans -- it looks like groundwork
has been laid to make the REPL's classpath pretty configurable (per-
project, etc). Is it reasonable to make that change temporarily until
that more flexible approach is fully implemented?

- Chas

[Eric Thorsen]

I just added the project roots to the REPL classpath startups to
address this and to allow debugging of source from projects loaded in
the REPL. I'm just incorporating the latest clojure lib stuff into
enclojure and I'll cut a release.

I've been thinking about whether or not in practice, people need/want
the amount of configuration I was originally envisioning for the
REPL. I want to be able to define application boundaries (I guess you
use groups in NB) and be able to run REPL(s) that reflect the
classpaths of those applications.
Of course I also want to connect to running clojure applications with
a REPL as well.

I'll check out the debugger issue on 6.5 once I get this out.

Thanks!
Eric

[Chas Emerick]

Eric,

IMO, I think your initial vision was spot on (at least judging by the
code I've looked at -- I'm not clear on what "groups" are in NB --
maybe those are the Compile, Test, Debug, etc., configurations?).

FWIW, the two key things on my wishlist are (a) per-project repls, and
(b) ability to move between using the compile, test, and debug
classpaths (not necessarily at runtime).

Thanks,

Chas

On Aug 29, 6:07 pm, Eric Thorsen <ethor...@thortech-solutions.com>
wrote: