- Loading...
...
Where available, the list provides links to further resources, like JEPs, mailing list threads or JBS issues.
JEP 158 may change log message formats and possibly the meaning of some JVM options.
...
JEP 245 may affect code that
...
passes invalid flag arguments to the JVM. It validates the arguments to all JVM command-line flags so as to avoid crashes, and ensured that appropriate error messages are displayed when they are invalid.
Users who are using any of the flags that are being removed will have to update their JVM-startup command lines. If they are moving from JDK 8 to JDK 9 then they will already have seen warning messages and thus should not be surprised. For a detailed list of the flags and flag combinations that have stopped working in JDK 9, please consult the JEP text.
JEP 220 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.
JEP 223 may affect code that relies on the old version string scheme to distinguish major, minor, and security-update releases
...
JEP 231 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.
JEP 240 may affect code that relies on the removed hprof
agent library as part of the JDK.
JEP 241 may affect code that relies on the removed experimental, unsupported, and out-of-date jhat tool.
JEP 213 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.
...
.
JEP 249 may affect code connecting to TLS servers that cannot accept the status_request
or status_request_v2
TLS extensions. It implements OCSP stapling via the TLS Certificate Status Request extension (section 8 of RFC 6066) and the Multiple Certificate Status Request Extension (RFC 6961). The OCSP stapling feature will be enabled by default in the JDK with this implementation.
JEP 236 may affect code that uses internal classes in the jdk.nashorn.internal.ir
package and its sub-packages.
JEP 158 may change log message formats and possibly the meaning of some JVM options.
JEP 252 may affect code that uses locale-sensitive services such as date, time, and number formatting which may behave differently for locales not supported in JDK 8.
...
...
214 may affect code that
...
JEP 217 may affect source code that uses annotations due to the refactoring of the javac
annotation pipeline, which should not be externally noticeable except where bugs were fixed and correctness improved.
...
relies on the removed GC combinations.
Users who are using any of the flags that are being removed will have to update their JVM-startup command lines. If they are moving from JDK 8 to JDK 9 then they will already have seen warning messages and thus should not be surprised. For a detailed list of the flags and flag combinations that have stopped working in JDK 9, please consult the JEP text.
JEP 231 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.
JEP 240 may affect code that relies on the removed hprof
agent library as part of the JDK.
JEP 241 may affect code that relies on the removed experimental, unsupported, and out-of-date jhat tool
...
.
JDK-8037739 may affect code that uses types from java.awt.peer and java.awt.dnd.peer packages.
All methods that refer to types defined in the java.awt.peer and java.awt.dnd.peer packages (the "peer types") will be removed from the Java API in Java SE 9. Application code which calls any such method which accepts or returns a type defined in these packages will no longer link. This is a BINARY incompatible change.
JDK-8029806 may affect code that uses the Packer/Unpacker addPropertyChangeListener and removePropertyChangeListener methods, which were deprecated in JDK 8, and removed in JDK 9.
JDK-8029805 may affect code that uses the LogManager addPropertyChangeListener and removePropertyChangeListener methods, which were deprecated in JDK 8, and removed in JDK 9.
JDK-8029904 may affect code that uses the com.sun.security.auth.callback.DialogCallbackHandler, which was deprecated in JDK 8, and removed in JDK 9.
JDK-8011044 may affect source code that uses javac -source or -target options below 6/1.6 to compile.
JEP 213 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.
JEP 217 may affect source code that uses annotations due to the refactoring of the javac
annotation pipeline, which should not be externally noticeable except where bugs were fixed and correctness improved.
JEP 224 may affect source code with Javadoc comments since the -Xdoclint
feature of javadoc
will be modified to validate input comments based upon the requested markup.
...