Navigation:
Java SE Development Kit (JDK) 23.0.1 freeware
... various platforms, making it a cornerstone for modern software engineering. ...
| Author | Oracle |
| Released | 2024-10-16 |
| Filesize | 228.00 MB |
| Downloads | 452 |
| OS | Windows 11, Windows Server 2019, Windows Server 2016, Windows 10 64 bit, Windows Server 2012 R2, Windows Server 2012, Windows 8 64 bit |
| Installation | Instal And Uninstall |
| Keywords | Java platform, Java Development Kit, JDK platform, Java, JDK, development, applet |
| Users' rating (10 rating) |
Java SE Development Kit (JDK) Free Download - we do not host any Java SE Development Kit (JDK) torrent files or links of Java SE Development Kit (JDK) on rapidshare.com, depositfiles.com, megaupload.com etc. All Java SE Development Kit (JDK) download links are direct Java SE Development Kit (JDK) download from publisher site or their selected mirrors.
| 23.0.1 | Oct 16, 2024 | New Release | Notable Issues Resolved: install/install: ➜ JDK RPM Upgrade Leaves Orphan Alternatives Entry (JDK-8336107 (not public)) Fixed the issue with entries in the "java" and "javac" groups not being properly managed during an RPM upgrade. Upgrading from an older Java RPM installed into a shared directory (/usr/lib/jvm/jdk-${FEATURE}-oracle-${ARCH}) to a Java RPM installing into a version-specific directory (/usr/lib/jvm/jdk-${VERSION}-oracle-${ARCH}), results in the older Java entries in the "java" and "javac" groups not being deleted. The issue does not manifest until the new Java is uninstalled. When it is uninstalled and Java from the lower release is installed, running Java commands like java or keytool without the full path specified will result in the "command not found" error. For example, install 21.0.3; upgrade it to 21.0.4; uninstall 21.0.4; install any Java update of 17 or 11 or 8 release; run "java" from the command line. The command will fail with the "command not found" error. Manually delete orphan Java entries in the "java" and "javac" groups to workaround the issue. Other Notes: core-libs/java.net: ➜ New Default Limits in the JDK HTTP Implementations (JDK-8328286 (not public)) New Default limits have been added to HTTP in the JDK. The JDK built-in implementation of the legacy URL protocol handler for HTTP, HttpURLConnection, and the new HttpClient, in the module java.net.http, now have a default limit on the maximum response headers size they will accept from a remote party. The limit is set by default at 384kB (393216 bytes) and is computed as the cumulative size of all header names and header values plus an overhead of 32 bytes per header name value pair. The default value of the limit can be changed by specifying a positive value with the jdk.http.maxHeaderSize system property on the command line, or in the appropriate conf.properties or net.properties file. A |
| 23 | Sep 18, 2024 | New Release | Major New Functionality: Primitive Types in Patterns, instanceof, and switch (Preview): Enhance pattern matching by allowing primitive type patterns in all pattern contexts, and extend instanceof and switch to work with all primitive types. This is a preview language feature. Module Import Declarations (Preview): Enhance the Java programming language with the ability to succinctly import all of the packages exported by a module. This simplifies the reuse of modular libraries, but does not require the importing code to be in a module itself. This is a preview language feature. Flexible Constructor Bodies (Second Preview): In constructors in the Java programming language, allow statements to appear before an explicit constructor invocation, i.e., super(..) or this(..). The statements cannot reference the instance under construction, but they can initialize its fields. Initializing fields before invoking another constructor makes a class more reliable when methods are overridden. This is a preview language feature. Implicitly Declared Classes and Instance Main Methods (Third Preview): Evolve the Java programming language so that beginners can write their first programs without needing to understand language features designed for large programs. Far from using a separate dialect of the language, beginners can write streamlined declarations for single-class programs and then seamlessly expand their programs to use more advanced features as their skills grow. Experienced developers can likewise enjoy writing small programs succinctly, without the need for constructs intended for programming in the large. This is a preview language feature. Libraries Previews and Incubator: Class-File API (Second Preview): Provide a standard API for parsing, generating, and transforming Java class files. This is a preview API. Stream Gatherers (Second Preview): Enhance the Stream API to support custom intermediate operations. This will allow stream pipelines to transform data in ways that |
| 22.0.2 | Jul 16, 2024 | New Release | JDK 11.0.23 contains IANA time zone data 2024a which contains the following changes: Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. Vostok, Antarctica changed time zones on 2023-12-18. Casey, Antarctica changed time zones five times since 2020. Code and data fixes for Palestine timestamps starting in 2072. A new data file zonenow.tab for timestamps starting now. Kazakhstan unifies on UTC+5 beginning 2024-03-01. Palestine springs forward a week later after Ramadan. zic no longer pretends to support indefinite-past DST. localtime no longer mishandles Ciudad Juárez in 2422. New Features: security-libs/javax.crypto ➜ Update XML Security for Java to 3.0.3 (JDK-8319124): The XML Signature implementation has been updated to Santuario 3.0.3. Support for four new SHA-3 based RSA-MGF1 signature methods have been added: SHA3_224_RSA_MGF1, SHA3_256_RSA_MGF1, SHA3_384_RSA_MGF1, and SHA3_512_RSA_MGF1. While these new algorithm URIs are not defined in javax.xml.crypto.dsig.SignatureMethod in the JDK update releases, they may be represented as string literals in order to be functionally equivalent. SHA-3 hash algorithm support was delivered to JDK 9 via JEP 287. Releases earlier than that may use third party security providers. Additionally, support for the following EdDSA signatures has been added: ED25519 and ED448. While these new algorithm URIs are not defined in javax.xml.crypto.dsig.SignatureMethod in the JDK Update releases, they may be represented as string literals in order to be functionally equivalent. The JDK supports EdDSA since JDK 15. Releases earlier than that may use 3rd party security providers. One other difference is that the JDK still supports the here() function by default. However, we recommend avoiding the use of the here() function in new signatures and replacing existing signatures that use the here() function. Future versions of the JDK will likely disable, and eventually remove, support for this function, as it cannot be supported using |
