Re: Proposed New Structure (starter for 10)

Stephen Leake writes:
> [email protected] (Phillip Lord) writes:
>
>> Stephen Leake <[email protected]> writes:
>>
>>> [email protected] (Phillip Lord) writes:
>>>
>>>> After this my vision is subtly different. I believe that JDEE should be
>>>> relatively small and do as little as possible, while allowing Emacs and
>>>> the environment to do most or all of the things that you speak off.
>>>
>>> +1. However, JDEE needs to provide some things to "the rest of Emacs" to
>>> leverage that properly.
>>>
>>>> So, project support. Eric has already mentioned EDE. 
>>>
>>> JDEE needs to provide an EDE java project.
>>
>> I think this is sounds sensible, but I am not sure what it would bring.
>> In particular, I'd be worried if it involves duplicating information
>> between Emacs and what-ever build tool is being used (probably maven),
>> unless we know how to completely automate this.
>
> That's the point of the EDE project; it would get whatever info Emacs
> needs from maven (by reading files or calling an external tool; I don't
> know what maven provides in that way), and deliver it to Emacs via the
> EDE API.

FWIW, upstream CEDET has some support for Java projects in EDE (ant.el,
java-root.el, jvm-base.el, and maven2.el). I did not merge them to Emacs
because I was unsure how usable/stable they are.

-David


------------------------------------------------------------------------------