- Loading...
...
JDK 9 Early Access builds might may also be provided by third parties. Oracle publishes regular JDK 9 builds at http://jdk9.java.net, for example.
...
Some of the changes targeted for JDK 9 might may affect code that relies on deprecated, removed, unsupported, internal or unspecified functionality. The list below has been compiled from the list of JEPs targeted for JDK 9 and other resources. It is not an exhaustive list of changes - there may be other changes you run into that have not been listed here.
...
This JEP might may change log message formats and possibly the meaning of some JVM options.
This JEP might may affect code that relies on the removed GC combinations.
...
This JEP might may affect code that relies on the removed endorsed-standards override mechanism, the removed extension mechanism, and the existence of rt.jar and tools.jar files as well as the old directory layout of files in the JDK & JRE installation image.
This JEP might may affect code that relies on the old version string scheme to distinguish major, minor, and security-update releases.
This JEP might may affect code that relies on the removed ability to request, at JRE launch time, a version of the JRE that is not the JRE being launched.
This JEP might may affect code that relies on the removed hprof agent library as part of the JDK.
This JEP might may affect code that relies on the removed experimental, unsupported, and out-of-date jhat tool.
This JEP might may affect source code that uses underscore ("_") as an identifier. Its use generated a warning as of Java SE 8, and has been turned into an error in JDK 9.
JEP 221 may affect code that uses the Doclet API. It replaces the Doclet API with a simpler design that leverages newer alternative APIs with improved functionality, and updates the standard doclet to use it.
...