Incompatibilities arising out of this release are marked accordingly.ĭefault methods in interfaces do not cause eager interface initialization For more information, see Deprecated APIs and Features Removed from JDK 8.Ī Maintenance Release of Java SE 8 was performed in March 2015. While these are incompatibilities, they have been called out in separate lists. Note that some APIs have been deprecated in this release and some features have been removed entirely. This section describes Java SE 8 incompatibilities in the Java Language, the JVM, or the Java SE API. However, there are some minor potential incompatibilities in the JRE and JDK that involve rare circumstances and 'corner cases' that are documented here for completeness. Almost all existing programs should run on Java SE 8 without modification. Java SE 8 is strongly compatible with previous versions of the Java platform. Incompatibilities between Java SE 8 and Java SE 7 The Rhino javascript engine has been replaced with the Nashorn javascript engine. The following document has information on changes to the Java Language Specification (JLS) and the Java VM Specification (JVMS). Version 52.0 class files produced by a Java SE 8 compiler cannot be used in earlier releases of Java SE. The class file version for Java SE 8 is 52.0 as per the JVM Specification. The Java class file format has been updated for the Java SE 8 release. For this reason, it is recommended that code is written in such a way so that it does not depend on unspecified behavior: In this scenario, the problem is not an incompatibility in the platform, is it a bug in the code.

There are aspects of the platform's behavior that are intentionally unspecified and the underlying implementation may change in a platform release. In its simplest form, behavioral compatibility means that with the same inputs a program performs the same (or an equivalent) operation under different versions of libraries or the platform. For more details, see Why Developers Should Not Write Programs That Call 'sun' Packages.įor a list of deprecated APIs, see Deprecated APIs. Developers importing from sun.* packages do so at their own risk. These APIs are not intended for use by developers. Some APIs in the sun.* packages have changed. It is recommended that programs be modified to eliminate the use of deprecated APIs. The javac compiler generates a warning message whenever one of these is used, unless the -nowarn command-line option is used.

See Incompatibilities between Java SE 8 and Java SE 7 and Incompatibilities between JDK 8 and JDK 7 for information.ĭeprecated APIs are interfaces that are supported only for compatibility with previous releases. However, implementation of some Java SE 8 features required changes that could cause code that compiled with Java SE 7 to fail to compile with Java SE 8. In general, the source compatibility policy is to avoid introducing source code incompatibilities. If these are used in a source file, that source file cannot be compiled on an earlier version of the Java platform. Java SE 8 includes new language features and platform APIs. Class files built with the Java SE 8 compiler will not run on earlier releases of Java SE. Except for the noted incompatibilities, class files built with the Java SE 7 compiler will run correctly in Java SE 8. Java SE 8 is binary-compatible with Java SE 7 except for the incompatibilities listed below. Incompatibilities in J2SE 5.0 (since 1.4.2).To examine Java SE 8 incompatibilities with earlier Java versions, you must trace incompatibilities through the listed files, in order. For example, this compatibility page reports only Java SE 8 incompatibilities with Java SE 7, and not with previous versions. The following compatibility documents track incompatibility between adjacent Java versions. 'Incompatibilities between JDK 8 and JDK 7'.'Incompatibilities between Java SE 8 and Java SE 7'.

Java 8 vs java 16