From f0e3dacf470d4d94b6de41b863172304ce016d3a Mon Sep 17 00:00:00 2001
From: Reinier Zwitserloot <r.zwitserloot@projectlombok.org>
Date: Fri, 1 Aug 2025 00:09:00 +0200
Subject: [PATCH] [build] vm-finder no longer blindly continues if trying to
 find an unknown VM version:

find-vm had the annoying property that on `/usr/libexec/java_home` based systems (Such as macs), trying to find the location of an unknown VM version just gave you the default, meaning `ant test.javac25` would run on 24. Now, it errors.
---
 buildScripts/vm-finder.ant.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/buildScripts/vm-finder.ant.xml b/buildScripts/vm-finder.ant.xml
index 2a33b2b8..94682fa4 100644
--- a/buildScripts/vm-finder.ant.xml
+++ b/buildScripts/vm-finder.ant.xml
@@ -62,7 +62,7 @@ and rerun the build; this build is capable of finding VMs automatically on many
 		<local name="java_home.result" />
 		<exec newenvironment="true" executable="${exe.java_home}" errorproperty="discard" outputproperty="java_home.answer" failifexecutionfails="false" resultproperty="java_home.result">
 			<env key="floobargle" value="FOO" /> <!-- we do not want JAVA_HOME to be set. This requires newenvironment="true" AND some sort of env value -->
-			<arg value="-v" />
+			<arg value="-Fv" />
 			<arg value="${find-vm.version}" />
 		</exec>
 		<condition property="jvm.loc" value="${java_home.answer}">