Phillip Lord <phillip.l...@newcastle.ac.uk> writes: > So, I wanted to put some meat onto the bone of my proposed new > structure for JDEE. > > It doesn't work yet, of course, but I think that it can in a relatively > short space of time. > > https://github.com/phillord/jde-with-clojure-backend
I have advanced this somewhat now and would be interested in opinions. I now have a worked nREPL connection to a live JVM running over the project. This provides the equivalent of the "beanshell interpreter" from a user perspective (i.e a shell) and can also be used to drive JVM interaction for things like introspection. Unlike, beanshell, I think we can easily support class reloading (i.e. live update the JVM for newly compiled classes), and extension of the classpath (so we can add new maven dependencies without restarting). We should be able to steal a lot of work from Cider (it's stacktrace support is nice!). The build is a little baroque at the moment, although it requires only standard tools, so is clean. From a user perspective, it will require maven, but no other downloads (once it's on Maven central). It's maven agnostic, though, so we *should* be able to support gradle, ant, any other build system or none with a little work. I've renamed jde-interactive to jdee-live and removed my minimal ELPA compliant minimal jde as that is pointless now. My plan for the future is to get one vaguely useful tool working, so I can test interaction with the Clojure based middleware, then stop, until it is clear that this is the way forward. Thoughts welcome! Phil ------------------------------------------------------------------------------ _______________________________________________ jdee-devel mailing list jdee-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jdee-devel
