From c639ae5d201518545568a76f8b546ec7e63ae667 Mon Sep 17 00:00:00 2001 From: Elliotte Rusty Harold Date: Thu, 23 Jul 2026 11:52:30 +0000 Subject: [PATCH] Clarify IfMatch behavior in JDK discovery docs --- src/site/apt/toolchains/jdk-discovery.apt.vm | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/src/site/apt/toolchains/jdk-discovery.apt.vm b/src/site/apt/toolchains/jdk-discovery.apt.vm index 692dc9a..dbf9a5d 100644 --- a/src/site/apt/toolchains/jdk-discovery.apt.vm +++ b/src/site/apt/toolchains/jdk-discovery.apt.vm @@ -69,9 +69,10 @@ JDK Toolchain discovery mechanism * <<>>: set to the comma separated list of <<>>> matching environment variables - The <<>> goal finds a matching JDK. - The config below allows using the current JDK, or any other discovered JDK >= 17. - The current JDK can be kept for speed, but JDK 17 or higher will be used if the current JDK is older than 17: + The <<>> goal finds a matching JDK. The config below selects a JDK + that satisfies the version range [17,). With the default IfMatch mode, the current JDK is used + directly when it meets the requirement (faster). If the current JDK does not satisfy the + requirement, a matching discovered JDK is selected instead. +---+