HotSpot 的反击：JEP 544 会终结 GraalVM 的启动性能垄断吗？
HotSpot JVM 迎来了激动人心的时刻：JEP 544: Ahead-of-Time Code Compilation 刚刚被提议纳入 Java 28。它有望让 HotSpot AOT 缓存获得足以媲美 GraalVM 的启动性能，而且完全不必承受 GraalVM 的种种艰辛。但训练 AOT 缓存与 GraalVM 的预编译并不相同，那么两者究竟孰优孰劣？15 个月后 SBOM 将成为强制要求，而你的 SBOM 很可能是错的。
2027 年 12 月 11 日，《欧盟网络弹性法案》（EU Cyber Resilience Act）中的 SBOM 义务将开始生效。这意味着，如果你想在欧盟发行软件，很快就需要一份 SBOM。这不仅是欧盟的要求，更是一场以这种声明式方法强化供应链安全的全球性趋势：美国自 2021 年起就要求联邦软件供应商提供 SBOM，CISA/NSA/FBI 也在今年 7 月发布了更新版的 SBOM 最低要素。
把 SBOM 做对并不容易，而当你还需要为软件交付安装程序时，难度更会进一步加大。现在该怎么办？让我们一起来看一看。
Migrating to install4j 12
In most cases, migrating to install4j 12 usually just involves opening and saving your project with the install4j 12 IDE. Nevertheless, there are some considerations with respect to backward compatibility and some behavioral changes.
With Temurin 24.0.2, Adoptium JDKs can again be modularized by install4j
This year we had some dramatic moments starting in April with the release of Temurin 24.0.0 from Adoptium, our default JDK bundle provider. In this blog post we celebrate the happy conclusion of this incident.
JEP 493 follow-up: install4j 11.0.4 is ready for separate JMOD bundles in Eclipse Temurin 24.0.2
Two months ago, I wrote about how JEP 493 threatened cross-platform JRE bundle creation by allowing JDK vendors to omit JMOD files from their distributions. Without JMOD files, tools like install4j cannot build cross-platform runtime images. This had the potential to seriously disrupt functionality for our users.
Caching auto-provisioned install4j distributions in CI pipelines
Starting with install4j 11.0, integrating install4j into your build system has become much easier: The Gradle, Maven, and Ant plugins can now auto-provision the install4j distribution. This means the plugins will download and cache the appropriate install4j version automatically, so you no longer need to install install4j manually.
Cross-platform JRE bundle creation under threat from JEP 493
One of the most valuable capabilities introduced with the Java module system in Java 9 is its support for creating custom runtime
images with jlink. Developers can include only the modules they need, resulting in lightweight JRE bundles tailored to the
requirements of their applications. Using the --module-path option, it has even been possible to generate those runtime
images for different operating systems from a single host machine.
With Java 24, JEP 493 introduces a change that significantly impacts this workflow.
JDK vendors can now configure builds without .jmod files, as jlink can optionally extract the required resources
from the lib/modules jimage file. While this change reduces the size of the JDK by about 25%, it also removes critical support
for cross-platform linking.
Improvements for macOS App Store submissions in install4j 11.0.2
install4j 11.0.2 introduces several new features to simplify macOS App Store submissions, including automated entitlement handling for TestFlight, improved support for local testing with development provisioning profiles, and dynamic bundle versioning for easier resubmission of builds.
Migrating to install4j 11
In most cases, migrating to install4j 11 usually just involves opening and saving your project with the install4j 11 IDE. Nevertheless, there are some considerations with respect to backward compatibility and some behavioral changes.
Namespace awareness of XML actions in install4j
This post explains an exceptional backward-incompatibility in the install4j 10.0.9 release. This was necessary due to a change in install4j 10.0.8 that was intended to fix the corruption of namespaced XML documents by modifying XML actions.