Community
Participate
Working Groups
I'll insert a screen shot that gives you the details.
Created attachment 1351 [details] Context is a static method in a class that's badly indented.
moving to JDT CORE
Filtering with enclosing types is guilty. class X { void bar(){ new Object(){ void foo(){ getClas<CODE ASSIST> } } } }
Actually, the code assist infrastructure effectively find 2 legite matches, but the UI doesn't present the difference. First match would be 'this.getClass()' --> X$1.class Second match would be 'X.this.getClass()' --> X.class The second match completion name would cause insertion of qualified X.this. Back to JDT/UI.
Candidate fpor F4
defer
A solution would be to show getClass() for this.getClass() X.this.getClass() for X.this.getClass()
Reopening for 2.1 consideration
Still an issue in 3.0 M2
Removing the 'readme' keyword: this is to minor to put it into the README.
Still an issue in 3.5 M7.
*** Bug 289976 has been marked as a duplicate of this bug. ***
*** Bug 295229 has been marked as a duplicate of this bug. ***
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.