Community
Participate
Working Groups
Build Identifier: 20110218-0911 javac compiles the code below, whereas Eclipse shows a "The field Foo.Bar.BAZ is not visible" error. ************************** public class Foo { public @interface Annotation { String value(); } @Annotation(Bar.BAZ) private static final class Some { } public static class Bar { private static final String BAZ = "foo"; } } Reproducible: Always
If Bar is defined outside of the class Foo, then javac reports the same visibility issue. In Eclipse, if I use Bar.BAZ inside a static field of Some, then it compiles fine: private static final class Some { static Object o = Bar.BAZ; } this looks inconsistent. Srikanth, please let me know what you think.
It compiles fine in Eclipse if the compliance is 1.6 or above. Could you please confirm that ?
I can still see the problem with 1.6 compliance.
It works in compliance 1.6 or above because the type annotation is resolved during annotation processing. If it doesn't, then the annotation processing should be disabled. This seems to be related to the fix for bug 316456. Srikanth, please take a look.
This should fail: @interface Annotation { String value(); } class Bar { private static final String BAZ = "foo"; } public class X { @Annotation(Bar.BAZ) private static final class Some {} } So it looks like private fields defined within the top level type can be accessed inside member types' annotations. This should also fail: public class X { @interface Annotation { String value(); } static class Bar { private static final String BAZ = "foo"; } } class Y extends X { @Annotation(Bar.BAZ) private static final class Some {} } Also annotation processing should not have any impact on this resolution.
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.
