Community
Participate
Working Groups
When the cursor is positioned on a local variable representing an object, and "Open Declaration" is selected, e.g. from the pop-up menu, Eclipse opens the file where the variable's class is declared. Instead, Eclipse should just jump to the position of the local variable's declaration. When the local variable has a primitive type, nothing whatsoever happens.
This is the intended behavior. Currently, we do not have an element representation for local variables (which is what we answer back from codeselect). A text range would be more generic, but less informative for clients (like search references to selection).
Forgot to mention that we plan to address this issue for 3.0.
*** Bug 37511 has been marked as a duplicate of this bug. ***
Similarly. If you search for references of a local variable(e.g. "foo" below), it is the type that is search for in the entire project. public class Foo { int foobar; public void xxx() { Object foo; } }
*** Bug 39361 has been marked as a duplicate of this bug. ***
ICodeAssist.codeSelect(...) now returns an ILocalVariable when the selection is a local variable reference/declaration. UI side should be fixed (see bug 45444) Searching local variables is captured in bug 43967. Tooltip for a local variable still doesn't work. Entered bug 45445. Marking this bug as fixed as the JDT/Core side is now implemented.
*** Bug 3345 has been marked as a duplicate of this bug. ***
Verified.