Community
Participate
Working Groups
Completion at '|' completes as Inner when C.Inner is required due to the scope of the type annotation. (And no supporting import is added if content assist preferences specify import over qualifier.) @a.B(In|) public class C { static class Inner {} } package a; import java.lang.annotation.*; @Target(ElementType.TYPE) public @interface B { Class<?> value(); } ScopeAnalyzer.getDeclarationsInScope is returning a binding for "Inner" and other members of C when a type annotation does not have visibility to type members.
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. If you have further information on the current state of the bug, please add it. 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.
This still applies to 4.14. Another curious behaviour is that if I leave "Inner" and then use code assist to complete "Inner.class" (at Inner.|, or Inner.c| or Inner.cl| and so on), "javassist.runtime.Inner" is automatically imported (that's a class I have in my classpath). In other words, JDT ignores C.Inner completely and adds the import when completing the .class constant, rather than the Inner type name.
Still applies to 4.22.
