Raul Acevedo writes:
> Looking at the JDEE source, it looks like it just doesn't know about
> symbols in interfaces at all. In particular, jde-open-jump-to-class
> only knows to look in the parent class, but it doesn't consider any
> implemented interfaces, either in the current class or in any parent
> class. Is this a known limitation?
>
Not to me. jde-open-jump-to-class has other limitations as well. I
plan to work on removing them as soon as possible. If anybody else
wants to jump in and help with this, feel free.
Paul
> Raul
>
> On Thu, 2004-10-07 at 15:49 -0700, Raul Acevedo wrote:
> > I have something like:
> >
> > public interface FooInterface {
> > public static final int FOO = 1;
> > }
> >
> > public class FooClass implements FooInterface {
> > public void doSomething() {
> > System.out.println("I'm doing something with " + FOO);
> > }
> > }
> >
> > If I put the cursor on the System.out.println, on FOO,
> > jde-open-class-at-point can't find the definition. If I write
> > FooInterface.FOO instead of FOO, it's fine, but FOO by itself is not.
> >
> > Raul
>
