updates to 26.0.0.2 blog

Author: navaneethsnair1

posts/2026-02-24-26.0.0.2.adoc

@@ -6,13 +6,10 @@ categories: blog
 author_picture: https://avatars3.githubusercontent.com/navaneethsnair1
 author_github: https://github.com/navaneethsnair1
 seo-title: Java Toolchains in Liberty Build Plugins in 26.0.0.2- OpenLiberty.io
-seo-description: This release introduces Java Toolchains support in the Liberty Maven and Gradle plugins, enabling developers to decouple the JDK used to run build tools from the JDK used to run the Liberty server. 
-blog_description: This release introduces Java Toolchains support in the Liberty Maven and Gradle plugins, enabling developers to decouple the JDK used to run build tools from the JDK used to run the Liberty server. 
+seo-description: This release introduces Java Toolchains support, enabling developers to decouple the JDK used to run build tools from the JDK used to run the Liberty server. 
+blog_description: This release introduces Java Toolchains support, enabling developers to decouple the JDK used to run build tools from the JDK used to run the Liberty server. 
 open-graph-image: https://openliberty.io/img/twitter_card.jpg
 open-graph-image-alt: Open Liberty Logo
-blog-available-in-languages:
-- lang: ja
-  path: /ja/blog/2026/01/27/26.0.0.2.html
 ---
 = Java Toolchains in Liberty Build Plugins in 26.0.0.2
 Navaneeth S Nair <https://github.com/navaneethsnair1>
@@ -52,7 +49,7 @@ Navaneeth S Nair <https://github.com/navaneethsnair1>
 // change the "IMAGE CAPTION" to a couple words of what the image is
 // // // // // // // //
 
-This release introduces Java Toolchains support in the Liberty Maven and Gradle plugins, enabling developers to decouple the JDK used to run build tools from the JDK used to run the Liberty server. 
+This release introduces Java Toolchains support, enabling developers to decouple the JDK used to run build tools from the JDK used to run the Liberty server. 
 
 // // // // // // // //
 // In the preceding section:
@@ -150,40 +147,34 @@ image::img/blog/blog_btn_stack.svg[Ask a question on Stack Overflow, align="cent
 [#java_toolchains]
 == Java Toolchains in Liberty Build Plugins
 
-In this update, Open Liberty introduces support for Java Toolchains in the Liberty Maven and Gradle plugins. This enhancement enables developers to decouple the JDK used to run their build tools from the JDK used to run the Liberty server, providing greater flexibility and environmental consistency.
+In the latest release of the Liberty build plugins, support has been added for Java Toolchains. This enhancement enables developers to decouple the JDK used to run their build tools(Maven or Gradle) from the JDK used to run the Liberty server and their applications. This provides greater flexibility and environmental consistency.
 
 === Java Toolchains support
 
-Open Liberty build plugins now support the standard Java Toolchain mechanism.
+The Liberty build plugins now support the standard Java Toolchain mechanism. 
 Previously, Liberty plugins were restricted to using the same Java version that was running Maven or Gradle.
-This often forced developers to use older JDKs for their entire build process if their application required a specific legacy runtime.
+This prevented developers from using more recent JDK versions for their build process if their applications required a specific older JDK version.
 
-With Java Toolchains, you can now run your build tool on a modern JDK (for example, Java 21). This helps ensure that the Liberty server and its tasks (such as dev mode or JSP compilation) execute using a different, specified JDK (for example, Java 8 or 11).
+With Java Toolchains, you can now run your build tool on a modern JDK (for example, Java 25). At the same time, Liberty server and all server operations can execute using a different, configured JDK (for example, Java 8).
 
 === Maven Plugin integration
 
 The Liberty Maven plugin now integrates seamlessly with the maven-toolchain-plugin. To use this feature, define your available JDKs in your `~/.m2/toolchains.xml` file. The plugin automatically detects and uses the toolchain that is specified in your project's `pom.xml` file.
+The Liberty Maven Plugin now integrates seamlessly with the maven-toolchain-plugin as of version 3.12.0.
+To use this feature, define your available JDKs in your `~/.m2/toolchains.xml` file and then configure `<jdkToolchain>` tag in `<configuration>`.
 
+The plugin automatically detects and uses the toolchain specified in your project’s `pom.xml` file.
 For detailed configuration steps and parameters, see the link:https://github.com/OpenLiberty/ci.maven/blob/main/docs/toolchain.md[Liberty Maven Plugin Toolchain documentation].
 
-[source,xml]
-----
-<plugin>
-    <groupId>io.openliberty.tools</groupId>
-    <artifactId>liberty-maven-plugin</artifactId>
-    <version>3.12.0</version>
-</plugin>
-----
-
 The plugin acknowledges the JDK vendor and version constraints that are defined in your Maven profiles, helping to ensure that your server environment remains consistent across different developer machines and CI/CD pipelines.
 
 === Gradle Plugin integration
 
-For Gradle users, the Liberty Gradle plugin now recognizes the native `java { toolchain { ... } }` configuration block. This configuration provides a unified way to manage Java versions across multi-project builds, where different services might have different runtime requirements.
+The Liberty Gradle plugin now recognizes the native `java { toolchain { ... } }` configuration block as of version 3.10.0. This configuration provides a unified way to manage Java versions across multi-project builds, where different services might have different runtime requirements.
 
-For technical specifics on how the plugin resolves these environments, see the link:https://github.com/OpenLiberty/ci.gradle/blob/main/docs/toolchain.md[Liberty Gradle Plugin Toolchain documentation].
+For detailed configuration steps and parameters, see the link:https://github.com/OpenLiberty/ci.gradle/blob/main/docs/toolchain.md[Liberty Gradle Plugin Toolchain documentation].
 
-When a toolchain is configured in your `build.gradle`, the Liberty plugin uses that specific Java runtime for all server-related tasks, including `libertyDev` and `libertyStart`.
+When a toolchain is configured in your `build.gradle`, the Liberty plugin uses that specific Java runtime for all server-related tasks(for example, `libertyDev` and `libertyStart`).
 
 === Try it now
 
@@ -236,7 +227,7 @@ java {
 == Notable bugs fixed in this release
 
 
-We’ve spent some time fixing bugs. The following sections describe the issues resolved in this release. If you’re interested, here’s the link:https://github.com/OpenLiberty/open-liberty/issues?q=label%3Arelease%3A26002+label%3A%22release+bug%22[full list of bugs fixed in 26.0.0.1].
+We’ve spent some time fixing bugs. The following sections describe the issues resolved in this release. If you’re interested, here’s the link:https://github.com/OpenLiberty/open-liberty/issues?q=label%3Arelease%3A26002+label%3A%22release+bug%22[full list of bugs fixed in 26.0.0.2].
 
 * link:https://github.com/OpenLiberty/open-liberty/issues/33927[IBM WebSphere Application Server Liberty is affected by a remote code execution vulnerability (CVE-2025-14914 CVSS 7.6)]
 * link:https://github.com/OpenLiberty/open-liberty/issues/32996["WARNING: package sun.security.action not in java.base" shows up in console.log starting in Java 24]