Java Development Kit for Mac 履歴ソフトウェアバージョン

winXmacソフトウェアコミュニティ Mac 開発者ツール Items 49 Freeware Rate 80

Java Development Kit for Mac、ソフトウェア教育、ソフトウェアダウンロード、ソフトウェアコミュニティ、Windowsソフトウェア、Macソフトウェア

Java Development Kit for Mac

Java Development Kit for Mac(JDK とも呼ばれる)は、Oracle Corporation によって作成され、定期的にサポートされている高度にプロフェッショナルなクロスプラットフォーム SDK プラットフォームです。世界中の Java SE、Java EE、および Java ME プラットフォーム開発者の特定の実装を提供するという目標を使用します。強力な開発サポートの...

Update:2021-03-18
Info:

What's new in this version:

New Features and Enhancements:
- JEP 396: Strongly Encapsulate JDK Internals by Default
- JEP 390: Warnings for Value-based Classes
- Add InvocationHandler::invokeDefault Method for Proxy's Default Method Support
- JEP 380: Unix domain sockets
- Day Period Support Added to java.time Formats
- Add Stream.toList() Method
- JEP 338: Vector API (Incubator)
- Improved CompileCommand Flag
- JEP 376: ZGC Concurrent Stack Processing
- Concurrently Uncommit Memory in G1
- JEP 387: Elastic Metaspace
- Signed JAR Support for RSASSA-PSS and EdDSA
- SUN, SunRsaSign, and SunEC Providers Supports SHA-3 Based Signature Algorithms
- jarsigner Preserves POSIX File Permission and symlink Attributes
- Added -trustcacerts and -keystore Options to keytool -printcert and -printcrl Commands
- SunPKCS11 Provider Supports SHA-3 Related Algorithms
- Improve Certificate Chain Handling
- Improve Encoding of TLS Application-Layer Protocol Negotiation (ALPN) Values
- TLS Support for the EdDSA Signature Algorithm
- JEP 397: Sealed Classes (Second Preview)
- JEP 395: Records
- JEP 394: Pattern Matching for instanceof
- JEP 392: Packaging Tool

Removed Features and Options:
- Removal of java.awt.PeerFixer
- Removal of Experimental Features AOT and Graal JIT
- Deprecated Tracing Flags Are Obsolete and Must Be Replaced With Unified Logging Equivalents
- Removed Root Certificates with 1024-bit Keys
- Removal of Legacy Elliptic Curves

Deprecated Features and Options:
- Terminally Deprecated ThreadGroup stop, destroy, isDestroyed, setDaemon and isDaemon
- Parts of the Signal-Chaining API Are Deprecated
- Deprecated the java.security.cert APIs That Represent DNs as Principal or String Objects

Other Notes:
- Line Terminator Definition Changed in java.io.LineNumberReader
- Enhanced Support of Proxy Class
- Module::getPackages Returns the Set of Package Names in This Module
- Support Supplementary Characters in String Case Insensitive Operations
- Proxy Classes Are Not Open for Reflective Access
- The Default HttpClient Implementation Returns Cancelable Futures
- HttpPrincipal::getName Returned Incorrect Name
- HttpClient.newHttpClient and HttpClient.Builder.build Might Throw UncheckedIOException
- (fs) NullPointerException Not Thrown When First Argument to Path.of or Paths.get Is null
- Incomplete Support for Unix Domain Sockets in Windows 2019 Server
- US/Pacific-New Zone Name Removed as Part of tzdata2020b
- Argument Index of Zero or Unrepresentable by int Throws IllegalFormatException.
- GZIPOutputStream Sets the GZIP OS Header Field to the Correct Default Value
- Refine ZipOutputStream.putNextEntry() to Recalculate ZipEntry's Compressed Size
- java.util.logging.LogRecord Updated to Support Long Thread IDs
- TreeMap.computeIfAbsent Mishandles Existing Entries Whose Values Are null
- Support for CLDR Version 38
- Added Property to Control LDAP Authentication Mechanisms Allowed to Authenticate Over Clear Connections
- LDAP Channel Binding Support for Java GSS/Kerberos
- Make JVMTI Table Concurrent
- IncompatibleClassChangeError Exceptions Are Thrown For Failing 'final' Checks When Defining a Class
- Object Monitors No Longer Keep Strong References to Their Associated Object
- Added 3 SSL Corporation Root CA Certificates
- Added Entrust Root Certification Authority - G4 certificate
- Upgraded the Default PKCS12 Encryption and MAC Algorithms
- Disable TLS 1.0 and 1.1
- C-Style Array Declarations Are Not Allowed in Record Components
- Annotation Interfaces May Not Be Declared As Local Interfaces
- DocLint Support Moved to jdk.javadoc Module
- Eliminating Duplication in Simple Documentation Comments
- Viewing API Documentation on Small Devices
- API Documentation Links to Platform Documentation
- Improvements for JavaDoc Search


Update:2021-01-20
Info:

What's new in this version:

IANA Data 2020d:
- JDK 15.0.2 contains IANA time zone data version 2020d. For more information, refer to Timezone Data Versions in the JRE Software.

Security Baselines:
- The security baselines for the Java Runtime Environment (JRE) at the time of the release of JDK 15.0.2 are specified in the following table:
- 7 - 1.7.0_45
- 6 - 1.6.0_65
- 5.0 - 1.5.0_55

JRE Expiration Date:
- The JRE expires whenever a new release with security vulnerability fixes becomes available. Critical patch updates, which contain security vulnerability fixes, are announced one year in advance on Critical Patch Updates, Security Alerts and Third Party Bulletin. This JRE (version 7u45) will expire with the release of the next critical patch update, scheduled for January 14, 2014.
- For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE (version 7u45) on February 14, 2014. After either condition is met (new release becoming available or expiration date reached), Java will provide additional warnings and reminders to users to update to the newer version. For more information, see JRE Expiration Date.

Blacklist Entries:
- This update release includes a blacklist entry for a standalone JavaFX installer.

JavaFX Release Notes:
- JavaFX is now part of JDK. JDK 7u45 release includes JavaFX version 2.2.45.
- JDK for Linux ARM
- A JDK for Linux ARM is also available in this release.

New Features and Changes:
- Protections Against Unauthorized Redistribution of Java Applications
- Starting with 7u45, application developers can specify new JAR manifest file attributes:
- Application-Name: This attribute provides a secure title for your RIA.
- Caller-Allowable-Codebase: This attribute specifies the codebase/locations from which JavaScript is allowed to call Applet classes.
- JavaScript to Java calls will be allowed without any security dialog prompt only if:
- JAR is signed by a trusted CA, has the Caller-Allowable-Codebase manifest entry and JavaScript runs on the domain that matches it.
- JAR is unsigned and JavaScript calls happens from the same domain as the JAR location.
- The JavaScript to Java (LiveConnect) security dialog prompt is shown once per Applet classLoader instance.
- Application-Library-Allowable-Codebase: If the JNLP file or HTML page is in a different location than the JAR file, the Application-Library-Allowable-Codebase attribute identifies the locations from which your RIA can be expected to be started.
- If the attribute is not present or if the attribute and location do not match, then the location of the JNLP file or HTML page is displayed in the security prompt shown to the user.
- Note that the RIA can still be started in any of the above cases.
- Developers can refer to JAR File Manifest Attributes for more information.

Restore Security Prompts:
- A new button is available in the Java Control Panel (JCP) to clear previously remembered trust decisions. A trust decision occurs when the user has selected the Do not show this again option in a security prompt. To show prompts that were previously hidden, click Restore Security Prompts. When asked to confirm the selection, click Restore All. The next time an application is started, the security prompt for that application is shown.
- See Restore Security Prompts under the Security section of the Java Control Panel.

JAXP Changes:
- Starting from JDK 7u45, the following new processing limits are added to the JAXP FEATURE_SECURE_PROCESSING feature.
- totalEntitySizeLimit
- maxGeneralEntitySizeLimit
- maxParameterEntitySizeLimit
- For more information, see the new Processing Limits lesson in the JAXP Tutorial.
- TimeZone.setDefault Change
- The java.util.TimeZone.setDefault(TimeZone) method has been changed to throw a SecurityException if the method is called by any code with which the security manager's checkPermission call denies PropertyPermission("user.timezone", "write"). The new system property jdk.util.TimeZone.allowSetDefault (a boolean) is provided so that the compatible behavior can be enabled. The property will be evaluated only once when the java.util.TimeZone class is loaded and initialized.

Bug-fixes:
- This release contains fixes for security vulnerabilities. For more information, see Oracle Critical Patch Update Advisory