Re: [jdee-devel] functionality development
Brought to you by:
paullandes
From: Phillip L. <phi...@ne...> - 2008-11-20 17:23:13
|
Thomas Finneid <tfi...@fc...> writes: > a couple of quick questions about functionality development in jdee. > > Question 1: > > The website states that jdee is a tool that integrates third party tools > into emacs for java development. What does that mean? > > - Does it mean that the third party packages provide complete > functionality that jdee interfaces or > - does it mean that jdee uses those third party packages to put together > a range of complete functionalities which did not previously exist. More the latter. JDE doesn't compile java, but does run javac. Likewise, ant and (I think) mvn and so on. Add all the standard emacs stuff (like version control support) and you have a development environment. > > The reason for the question is that I would like to help develop some > functionality for jdee, and I was thinking was to use perl to create the > functionality and then lisp code to integrate it into jdee. That would work; however, because you'd have to use the perl as an external command, the integration with emacs might not be as good as if you did it in lisp. Whether or not this is a problem depends on what you are trying to do. > What kind of tags program/functionality does jdee support or exists in jdee? > > I have been using the standard ctags/etags program and the standard > emacs tags functionality. But for java development it seems to lack some > features which make it more efficient. > > For example, a tag search does not seem to take context of a method call > into consideration. This means all possible getX() methods in the source > code is visited, one after another. What it should do is: if the method > call is prefixed with an instance reference or class name, it should > start the search in that class and expand outwards as appropriate. It > shold not f.ex. start in the class that is alphabetically first in the > tags list. Other things i feel is missing is that searches should > differentiate between interfaces and classes, one implementation of an > interface from another (in f.ex. a separate package) and so on > > If there is no tags program or emacs functionality to support this I > would like to help by developing this, I just need to know what is the > preferred approach to extend functionality. > There are a couple of things there. JDEE used to provide etags support for java. I don't think that it needs this any more as it's there by default. Gnu Global support would be nice to add; again I've not tried this. It's possible emacs support is already there. Finally, semantic builds a database which you can search. Again, not tried this. Sorry that this part of my answer is pretty useless; I tend to just grep when I need this functionality. Phil |