RFR 8149757:Implement Multi-Release jar aware JavacFileManager for javac

Steve Drach steve.drach at oracle.com
Thu Apr 7 22:24:46 UTC 2016


This is a new webrev incorporating several changes that both Jon and Jan suggested.

issue: https://bugs.openjdk.java.net/browse/JDK-8149757 <https://bugs.openjdk.java.net/browse/JDK-8149757>
webrev: http://cr.openjdk.java.net/~sdrach/8149757/webrev/index.html <http://cr.openjdk.java.net/~sdrach/8149757/webrev/index.html>

Thank you,

> Please review the changes required to make javac and the StandardJavaFileManager multi-release jar aware.  For javac, the version of the classes in a multi-release.jar is selected by the -release (or -target) command line option, or if the option is not present, javac’s default policy is used to select the version — typically the runtime version (i.e. version 9 is selected for JDK 9).  For the StandardJavaFileManager, the version is selected with the handleOption method.  See the tests for more detail.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/compiler-dev/attachments/20160407/9e145d6f/attachment-0001.html>

More information about the compiler-dev mailing list