After six months of development Oracle released Platform Java SE 18 (Java Platform, Standard Edition 17), as a reference implementation of which is an open project OpenJDK. With the exception of the removal of some outdated features in Java SE 18, reverse compatibility with the past releases of the Java platform are saved – most of the previously written Java projects without changes will be operational when started running the new version. Ready to install Java SE 18 build (JDK, JRE and Server JRE) Prepared for Linux (x86_64, aarch64), Windows (x86_64) and MacOS (x86_64, aarch64). Designed as part of the project OpenJDK Reference implementation java 18 fully opened under the GPLv2 license with the exceptions of GNU Classpath, allowing dynamic binding to commercial products.
Java SE 18 is assigned to the category of issues with a regular support period, updates for which will be released before the next release. As a branch with a long support period (LTS), you should use Java SE 17, updates for which will be released until 2029. Recall that since the release of Java 10, the project moved to a new development process, implying a shorter cycle of formation of new releases. New functionality is now developing in one constantly updated Master-branch , which includes ready-made changes and from which time Months are branched to stabilize new issues.
From innovations java 18 you can Tell :
- by default is involved UTF-8 encoding. Java APIs processing text data taking into account the symbol encoding will now use UTF-8 by default on all platforms, regardless of the system settings and the displayed locale. To return an old behavior in which the encoding is selected taking into account the system locale, you can use the “-dfile.encoding = compat” parameter.
- in the is enabled the com.sun.net.httpserver package, which includes the JWebServer utility and the library API with a simple realization HTTP server to recover static content (CGI and SERVLET-like handlers are not supported). The built-in HTTP server is not optimized for workloads and does not support access control and authentication, as it is aimed mainly to use during the development process to create prototypes, debugging and testing projects.
- in javadoc implemented Support for tag “ @ snippet