Community
Participate
Working Groups
Take a look at the Eclipse project I've zipped and uploaded to the URL given (File > Import > Existing Projects Into Workspace > Archive file). I receive a compilation error for a constant (public static final class variable) that is (1) referred to in another class, and (2) is initialized to its value using a static method (imported using a static import). I believe this has something to do with the order in which classes are built (see attached code). I've been getting around this bug by changing the source file, and re-saving it. That appears to fix it temporarily. Doing a clean build causes the error to reappear. I'm using Eclipse 3.3 M7 (Version: 3.3.0, Build id: I20070418-1012) with a Sun 1.5.0 compiler.
Created attachment 67466 [details] Eclipse project to reproduce the bug
Kent, Could you please have a look? This is an ordering issue in the full build. Recompiling only Foo fixes the compile error, but it is back on a new full build.
Created attachment 67495 [details] Proposed patch
Created attachment 67500 [details] Update patch Found another place where we access static imports possibly before they're resolved
+1.
Released into HEAD for 3.3RC1
Verified for 3.3RC1 with I20070516-1800.