From 96ca021c758da63ddfb00a7dff93f30417ebe616 Mon Sep 17 00:00:00 2001
From: Stefan Bodewig <bodewig@apache.org>
Date: Tue, 28 Dec 2021 18:46:15 +0100
Subject: [PATCH] properly describe how Ant reads environment variables

closes https://bz.apache.org/bugzilla/show_bug.cgi?id=65768
---
 manual/Tasks/property.html | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/manual/Tasks/property.html b/manual/Tasks/property.html
index 42250b9f8..df406b06b 100644
--- a/manual/Tasks/property.html
+++ b/manual/Tasks/property.html
@@ -319,10 +319,10 @@ deploy.url=http://${deploy.server}:${deploy.port}/
   variables it ran on Java 1.2 where <code>System.getEnv</code> didn't
   work. So we decided to start a command in a new process which prints
   the environment variables, analyzes the output and creates the
-  properties. Once Java 5 became our baseline we could have switched
-  to <code>getEnv</code> but it returned different results on some
-  platforms so we stuck with the command approach to remain backwards
-  compatible.
+  properties. With Ant 1.9.0 when we started to require Java 5 we switched back
+  to <code>System.getEnv</code> even though it returned different results on some
+  platforms. The commands described below are still used on OpenVMS or
+  if <code>System.getEnv</code> throws an exception.
 </p>
 <p>
   There are commands for the following operating systems implemented in