Description Andrew Clement 2010-06-30 15:09:11 EDT

Bug 266420 attempted to address this, where an ITD was using a private field within some target type so the warning about 'not read locally' shouldn't be put out for the field.  However, it seems in some situations, on full builds, the problem still occurs.  It has been seen on Windows and Linux.  In the Windows case on a full build of a Spring Roo petclinic app (roo 1.1.0m1). 

On an incremental build the warning disappears.

The logic to 'hide' this warning is in the AjProblemReporter which, on an attempt by the compiler to report the issue, checks if there is an aspect that has requested privileged access to the field.  in the failure situation the type doesn't report that is is affected by any aspects (so we don't find the privileged request).  This is weird because the program works and the other annotations indicate the type is advised correctly...