On Sat, Sep 12, 2015 at 8:18 AM, Peter Levart <peter.lev...@gmail.com> wrote: > > But even then you might have ended up with a Method in a non-public class, > so you were forced to use .setAccessible(true) to invoke it. >
That's right, that was the main issue here, we had not yet "forbid" setAccessible / removed suppressAccessChecks to prevent surprises like this. Java developers use it everywhere seemingly without care, so its not easy to cleanup.
