On 23 February 2010 08:08, 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).
Tobias -- thank-you for the answer. I can see that this is a sensible way to
accomplish this goal. Unfortunately, it probably means the feature will
never work in my environment. It's highly unlikely that I can compile the
code in a way that JDEE will be able to consume: the build products are not
standard desktop Java -- the code base is actually Research In Motion's
device code (where I work). We use our own VM and our own compiler suite, so
it's highly possible that built products wouldn't be compatible with the
JDEE tools. It's also highly probable that I couldn't just compile up
standard JAR files with standard Java tools pointed at our code.
At any rate, it's possible that some sort of solution could be found, but it
would probably involve investigation and possibly tooling that I'm not
really comfortably able to accomplish.
I was hoping that the JDEE suite could work only with the Java source
itself.
Oh well -- thanks for your explanation!
--
v.
------------------------------------------------------------------------------
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
