Right, everyone is too busy to do anything but the bare essentials at this 
point.  I'm very happy that we made as much progress as we did a few months ago 
(another thanks to the contributors).

I planned on starting (not extending) the Clojure work Phillip did but work 
keeps getting in the way.


On Oct 14, 2015, at 6:04 AM, Phillip Lord <phillip.l...@russet.org.uk> wrote:

> Troy Daniels <udalrich.scher...@gmail.com> writes:
> 
>> It seems there was a burst of design discussion and some prototyping a
>> month or two ago, which has died down to nothing recently.
> 
> Start of term for me, I'm afraid.
> 
>> I'm using this at work, and having something that is able to figure
>> out the project structure from Maven would be really useful. Useful
>> enough that I would be willing to put some time into helping develop
>> the capability. Do we have a clear idea of what we want to do, what
>> has already been done and what is needed? If we do not have a clear
>> roadmap on this, can someone give me a statement of what the current
>> state is, which will be faster than me looking through the new code to
>> understand what it does, and missing an important part because I don't
>> understand it?
> 
> Well, we currently have the beanshell based approach that JDEE has used
> for a long time. This works, and is okay, but I think is problematic in
> the long term.
> 
> I've build a system which reuses all the Clojure technology.
> 
> https://github.com/phillord/jde-with-clojure-backend
> 
> This gives us a shell running in the maven project environment, a
> mechanism for adding new functionality in the JVM (with Clojure), and a
> mechanism for interacting with that functionality in ELisp (via cider).
> We could clearly use this to replace beanshell, but at the moment, it is
> proof-of-principle only.
> 
> For me, this is an experiment. I'm not sure that I have the bandwidth to
> pull it forward into a roadmap, especially as I do not code Java
> routinely. I'm willing to support this process if someone else wants to
> take it forward.
> 
> Phil
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> jdee-devel mailing list
> jdee-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jdee-devel


------------------------------------------------------------------------------
_______________________________________________
jdee-devel mailing list
jdee-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jdee-devel

Reply via email to