I was lucky enough to have one laptop still un-upgraded. I did a clean build and test before and after the update and saw no change.
On Mon, May 24, 2010 at 3:22 AM, David Stuart < [email protected]> wrote: > I have just done the Java update and run the build and tests and have had > no problems > > > On 23 May 2010, at 20:03, Sean Owen wrote: > > > I am not seeing this error, before or after the Java update. > > > > It's a strange one -- sort of sounds like it's complaining it can't > > get at something that's public?? > > > > I assume you tried a clean build. > > > > You could try making that abstract class public instead of > > package-private. It doesn't really hurt to do that, and if it works > > around this for you, sure. > > > > On Sun, May 23, 2010 at 3:44 PM, Jeff Eastman > > <[email protected]> wrote: > >> Its Snow Leopard and the Java update #2 to 1.6.0_20 > >
