Accessing module internals from bytecode rewriting agent

Martin Buchholz martinrb at
Tue May 9 00:58:54 UTC 2017

Another way to think about transition to a new JDK is to treat the new
release JDK N as a "better JDK N-1".  You still target JDK N-1 at build
time but get performance and quality improvements from the JDK N runtime,
running along with JDK N-1 for years.  Then every small incompatibility is
a big nuisance.  It's an interesting thought experiment whether using two
releases to get to strong encapsulation might have been an easier
transition for users (but of course too late now and would have made jigsaw
implementers' lives tougher).

More information about the core-libs-dev mailing list