I’m sure versions of this newbie type question get asked again and again from time to time, but I just couldn’t pull together an answer for myself by sifting the CEDET list archives, so (apologies), I’ll ask away. 


What are some best practices for configuring CEDET for a Java-ish project, in order to achieve:


* Smart completion

* Symbol lookup

* File name lookup

* Cross-references


I should point out that my "project" (as is quite common) has many file types besides Java:  XML, HTML, JavaScript, some C/C++ code, etc., and I'd like to have a somewhat uniform Emacs view of all this.  That's partly why JDEE project files don't quite do the trick.


The problem I'm having is that the JDEE provides some version of these features, with some deficiencies, and seemingly with considerable overlap with CEDET.  Completion and symbol lookup exist, but are slow and only work for compiled classes.  Also, they only work for Java files, which is inadequate when a project has a mixture of other programming languages and file types.  File name lookup seems not to exist at all.  And JDEE has the xref database, but it's a little flaky (it pukes while parsing one of my files) and again, only works for Java files.


So, I'd prefer to use CEDET's features for these.  Evidently, it involves some combination of CEDET customizations, EDE project configuration, and maybe some use of idutils and/or GNU Global for good measure.  Unfortunately, I haven't yet figured out how to do this, despite staring at the CEDET documentation for a few days.  I'll keep plugging away at it, but I confess I'm badly in need of a clue on this.   Thanks in advance.  And I should say, I really am very impressed by CEDET (despite an imperfect understanding of it) and sense considerable power embedded in it.


All the best,

David Ventimiglia