Description David Whiteman 2003-07-09 17:16:21 EDT

I have had code for a long time that, in a static initalizer, "touches" another 
class so that its static initializer will run.  Here is an example:

public class Foo {
  static {
    Bar.class.getName();
  }
  public Foo() {
  }
  public static void main(String[] args) {
     new Foo();
  }
}

public class Bar {
  static {
    System.out.println("in bar");
  }
}

In Eclipse 2.1, running main() on Foo would have resulted in the statement "in 
bar" printing.  It appears that in the M1 build, the Bar.class.getName() has 
been optimized such that the Bar static initializer doesn't get run.  This has 
broken my code since I was relying on this behavior.  Is there some other way 
via reflection to force Bar's initialization?