On 02/23/2010 11:33 AM, Tim Visher wrote: > On Tue, Feb 23, 2010 at 8:08 AM, Tobias Gerdin<[email protected]> wrote: >> >> The JDEE extracts this kind of information from the compiled class >> files, so you need to tell it where to find them using the >> `jde-global-classpath' variable. >> >> After doing that jde-open-class-at-point and friends should work >> (assuming your project is built). > > Does that mean that the JDEE doesn't provide a way to give it a > project specific classpath? >
I am not certain of the nature of your problem, however, CEDET uses EDE to manage basic project data, and JDEE is not an EDE project. Linking the two would probably not be hard. An EDE wrapper would be pretty easy. Anyway, the EDE project basically just scopes any searches, and there are mode specific overloads for finding included souce files (ie. imports) that I don't think anyone has written to take advantage of Java's directory structure. Basically, for CEDET to work well with Java projects, it will take someone who uses java/jdee to try using it, and updating the various overloads to get it right. The defaults, however, may be sufficient for your uses. I just don't know, and was hoping a JDEE user might fill in gaps in my knowledge. Eric ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ jdee-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jdee-users
