You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by bo...@apache.org on 2021/12/28 17:46:49 UTC
[ant] branch 1.9.x updated: properly describe how Ant reads environment variables
This is an automated email from the ASF dual-hosted git repository.
bodewig pushed a commit to branch 1.9.x
in repository https://gitbox.apache.org/repos/asf/ant.git
The following commit(s) were added to refs/heads/1.9.x by this push:
new 96ca021 properly describe how Ant reads environment variables
96ca021 is described below
commit 96ca021c758da63ddfb00a7dff93f30417ebe616
Author: Stefan Bodewig <bo...@apache.org>
AuthorDate: Tue Dec 28 18:46:15 2021 +0100
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 42250b9..df406b0 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