jdee-emacs / jdee

The JDEE is an add-on software package that turns Emacs into a comprehensive system for creating, editing, debugging, and documenting Java applications.
GNU General Public License v2.0
424 stars 55 forks source link

Using "short" syntax for classpath does not work. #66

Open liar666 opened 8 years ago

liar666 commented 8 years ago

I was listing all the classes, one-by-one, in my Jdee Global Classpath.

Since it's very difficult to maintain, I decided to switch to "short"ened version when specifying the classpath.

Now, jdee is unable to import/complete most elements.

Picture below shows that my Jdee Global Classpath contains "~/Work/Code/heritrix-3.2.0/lib/*.jar" (top left), which contains ~/Work/Code/heritrix-3.2.0/lib/heritrix-modules-3.2.0.jar (bottom right), which contains "org/archive/modules/CrawlURI.class" (top right), however, Jdee tells me "No match for CrawlURI" when trying to automatically add the corresponding import: http://s1328.photobucket.com/user/liar6666/media/Bugs/GlobalClasspathBug_zpsciachthf.png.html?sort=3&o=0

liar666 commented 8 years ago

OK I read some Java docs and apparently, the syntax is not .jar, but . I've changed that but I still have a lot of classes that do no complete or import anymore.

liar666 commented 8 years ago

Hi again,

  1. I did some cleaning, removing libs that were in doubles in my dirs => does not change the behaviour
  2. I checked both jdee-import-find-and-import and jdee-complete:
    • import works generally better than complete
    • import does not work with IXMLConfigurable, returns "No[t] match for IXMLConfigurable". Might be related to the case? Like in issue #64 (for which I still have no working solution)...
    • complete does not work on LanguageUtilities.xxx, which is a class of mine containing many static methods => Completion does not take static methods into consideration?
liar666 commented 8 years ago
  • complete does not work on LanguageUtilities.xxx, which is a class of mine containing many static methods => Completion does not take static methods into consideration? It's really strange, I've just tested, it works with another class of mine ExceptionUtilities.xxx which also contains a lot of static methods... Both classes are in the same package & jar... I'm really lost here...