Skip to content

Clarify IfMatch behavior in JDK discovery docs #190

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
elharo merged 1 commit into from
Jul 27, 2026
Merged

Clarify IfMatch behavior in JDK discovery docs #190

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions src/site/apt/toolchains/jdk-discovery.apt.vm
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,9 +69,10 @@ JDK Toolchain discovery mechanism
* <<<env>>>: set to the comma separated list of <<<JAVA\{xyz\}_HOME>>>> matching environment variables


The <<<select-jdk-toolchain>>> 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 <<<select-jdk-toolchain>>> 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.

+---+
<properties>
Expand Down
Loading