I doubt it is to do with Java itself since I did not see this behavior. This shouldn't be a security issue.
I rather suspect a JUnit version issue somehow? On May 23, 2010 9:08 PM, "Jeff Eastman" <[email protected]> wrote: Good fix! I changed the AbstractTestVector class to public and it's happy now. In the Apple notes on the update, they did say they made improvements to security, so that must have been the issue. The subclasses are all in the same package though, so I would have thought leaving off the modifier would have been ok too, but I don't understand all the subtlties of Java inheritance. I'll commit the fix and move on to bigger fish to fry. On 5/23/10 12:03 PM, Sean Owen wrote: > > I am not seeing this error, before or after the Java upd...
