From 4bd5a24caf9e3714fe474592fab0d47823ad2bfc Mon Sep 17 00:00:00 2001
From: Christopher Ng <facboy@gmail.com>
Date: Mon, 21 Oct 2024 12:25:30 +0100
Subject: [PATCH] Fix bug in `vm-finder.ant.xml` when asking for vm location

The `<fail>` task had an invalid declaration - it can't have an `if` and a nested `<condition>`
---
 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 2a33b2b88a..050ee531e1 100644
--- a/buildScripts/vm-finder.ant.xml
+++ b/buildScripts/vm-finder.ant.xml
@@ -143,7 +143,7 @@ and rerun the build; this build is capable of finding VMs automatically on many
 			<matches pattern="^\s*$" string="${jvm.loc}" />
 		</condition>
 		<fail if="jvm.loc.aborted">aborted</fail>
-		<fail if="jvm.loc.invalid">.
+		<fail>.
 
 ERROR: That does not appear to be a valid location; ${jvm.loc}/bin/${exe.java} should exist.
 			<condition>