Here is a testcase which causes 1.1 javac to produce error (1.0.2 compiles fine)
It seems that the errors might be the result of change in semantics for
name resolution in 1.1 because of inner classes (though this test does
not use any).

abhilasha{pjajoo}557: cat -n Foo.java
     1 package Money;
     2
     3 public class Foo {
     4 }
abhilasha{pjajoo}558:
abhilasha{pjajoo}558: cat -n Money.java
     1 package Money;
     2
     3 public class Money {
     4 }
abhilasha{pjajoo}559:
abhilasha{pjajoo}559: javac -d . Foo.java Money.java
abhilasha{pjajoo}560:
abhilasha{pjajoo}560: cat -n Bug.java
     1 package Money;
     2
     3 public class Bug {
     4 Money.Foo obj;
     5 }
abhilasha{pjajoo}561:
abhilasha{pjajoo}561: javac -d . Bug.java
Bug.java:4: Class Money.Money. Foo not found in type declaration.
    Money.Foo obj;
                 ^
1 error
abhilasha{pjajoo}562:

This is a simplified example. The problem actually during creation
of machine generated bean adaptor (which has code fragment similar to
Bug.java above).

-Pramod

The problem is acute in our context as code for Bug.java is generated on
fly (in the process of writing an adaptor for the bean).