Description Andrew Clement 2006-03-17 05:29:57 EST

The code for determining whether compilation of a file has resulted in structural changes to the file has been changed recently to improve memory consumption.  We now store a compactstructurerepresentation of the bytecode for a class and on subsequent builds compare it with the new bytecode produced.  The new bytecode is processed using an Eclipse ClassReader object.  Unfortunately the compactstructure object is built using the resolvedtype information and not the classreader output - this leads to problems where methods/etc are in the bytecode but the resolvedtype has no knowledge of.  Two examples hit so far are:
this$0 - a field in inner types
access$0 - a method created for types with inner types that access private fields in their outer type.

I've patched things up to allow for these cases - longer term (if more cases crop up...) we may need to fix the compactstructure object such that it gets built from a classreader - then we will always be comparing appropriate data.

The problems with incorrect comparisons result in full builds when incremental builds would be sufficient.