>From: Steve Blackburn <###@###.###>
An error in my code generated the correct compiler error followed by
the compiler producing a java.lang.NullPointerExceptionand then the
compiler seemed to go into a strange state error messages suggesting
that the compiler was re-parsing the source and complaining that each
declaration had already beenmade. After fixing my casting error the
compiler once againproduced the nullPointerException not complaining
about thecasting error but otherwise generating the same error
messagesand the request for me to file a bug report. Further
testingsuggests that the problem was with the class files thatwere in
the directory from previous runs. Removing all classfiles from the
directory and recompiling solved the problem.In the context of the!
'stale' class files being removed the casting error was generated
correctly without the exception.
An error in my code generated the correct compiler error followed by
the compiler producing a java.lang.NullPointerExceptionand then the
compiler seemed to go into a strange state error messages suggesting
that the compiler was re-parsing the source and complaining that each
declaration had already beenmade. After fixing my casting error the
compiler once againproduced the nullPointerException not complaining
about thecasting error but otherwise generating the same error
messagesand the request for me to file a bug report. Further
testingsuggests that the problem was with the class files thatwere in
the directory from previous runs. Removing all classfiles from the
directory and recompiling solved the problem.In the context of the!
'stale' class files being removed the casting error was generated
correctly without the exception.