I just committed initial version of EDE support for Maven projects.
I took old version of proj-maven2, and extended it with automatic
classpath calculation using Maven itself. Now I'm able to open .java
file, and corresponding project will be loaded, providing name
completions using semantic/db-javap
There is a lot of todo in my list, but I hope, that even in this form,
it will help java devs.
The next thing that I want to do, is to refactor proj-maven2 to use
common base class for all JVM projects, plus to add ability to
re-calculate classpath if pom.xml was changed.
If you have any suggestion, please, write me directly, or (it's
better) to write here...
On Mon, Oct 15, 2012 at 6:19 PM, Alex Ott <alexott@...> wrote:
> Here is example of working name completion, where classpath
> information is obtained automatically from Maven:
> On Mon, Oct 15, 2012 at 11:32 AM, Alex Ott <alexott@...> wrote:
>> Hi again
>> I wrote simple prototype on the top of proj-maven2, that fetches
>> classpath information from Maven, and use it. I was able to get
>> completions working for fairly complex Hadoop project. I think, that
>> I'll refactor common parts into separate class, and will inherit all
>> JVM-based projects from it.
>> And I have following question - does semantic/db-javap.el will store
>> extracted information in cache or it will perform lookup in jar every
>> time I'll call completion?
>> On Sun, Oct 14, 2012 at 1:20 PM, Alex Ott <alexott@...> wrote:
>>> Hi all
>>> Last months I'm spending more time working on JVM-based projects
>>> (mostly Clojure, and Java). I see, that situation with Java in CEDET
>>> is improved, but it still lacks such things, as automatic classpath
>>> detection, etc.
>>> I'm thinking about restoring "obsolete" maven EDE project, but besides
>>> maven, I also use Leiningen for Clojure code, and I'm also thinking
>>> about support for other JVM-related build tools, like SBT for Scala,
>>> Graddle, etc. So, I want to ask developers on how it's better organize
>>> hierarchy for all these projects, so we'll avoid code duplication, and
>>> Java completion/SemanticDB would be able to obtain classpath
>>> information from any of these projects.
>>> I'm thinking about creating generic-java-project, that will have
>>> "classpath" slot inside, and it will be used by SemanticDB. And
>>> specific project types will fill this slot using project-specific
>>> tools, like 'lein classpath' for Leiningen, 'mvn
>>> dependency:build-classpath' for Maven, etc.
>>> What do you think?
>>> With best wishes, Alex Ott
>>> Twitter: alexott_en (English), alexott (Russian)
>>> Skype: alex.ott
>> With best wishes, Alex Ott
>> Twitter: alexott_en (English), alexott (Russian)
>> Skype: alex.ott
> With best wishes, Alex Ott
> Twitter: alexott_en (English), alexott (Russian)
> Skype: alex.ott
With best wishes, Alex Ott
Twitter: alexott_en (English), alexott (Russian)