Weird use case: compiling against dummy sun.misc.* class
Alex Buckley
alex.buckley at oracle.com
Fri May 20 16:18:37 UTC 2016
On 5/20/2016 9:13 AM, Alex Buckley wrote:
> If you have your own sun.misc.FOO on the classpath, then you DON'T want
> a module exporting sun.misc to be readable, because that module is where
> javac and the runtime will get sun.misc.* types from. So, no need to add
> readability of the jdk.unsupported module which is not read by default
> on JDK 9b118.
I (sort of) take that back -- jdk.unsupported will be read at runtime
since it exports at least one package without qualification, but I seem
to recall something about not making it readable by default at compile time.
Alex
More information about the jigsaw-dev
mailing list