ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 49366] Differences between system.getenv and Ant 1.8.1 <property env=""/>
Date Fri, 11 Jun 2010 12:56:26 GMT

--- Comment #4 from Dmitry A. Kuminov <> 2010-06-11 08:56:23
EDT ---
Here is the result of the ant-env.jar invocation on OS/2, as requested by 
Stefan Bodewig:

Detected OS_NAME: os/2
Detected OS_ARCH: x86
Detected OS_VERSION: 20.45
Detected Java Version: 1.5.0_07
Detected Java Vendor: Sun Microsystems Inc.
Detected Java VM Version: 1.5.0_07-b03
Detected Java VM Name: Java HotSpot(TM) Client VM


Note that BEGINLIBPATH is not a real environment variable to the effect that it
is not listed by the 'cmd /c set' command although it can be changed using the
'cmd /c set BEGINLIBPATH=<value>' command like any other environment variable.
Note also that this variable is not present in the LIBC's environ array on OS/2
(which means it's not part of the process environment at all and cannot be
acessed with getenv()/setenv(), there is a special Dos* API for that). The
reason why it appears in the System.getenv() map is because it is specifically
added there by the "native" code (I placed "native" in quotes because JDK 1.5
for OS/2 is only available as an Odin-based port where Odin is a Win32
emulation layer similar to Wine; so this comes from its GetEnvironmentStrings()
implementation AFAIR).

And there is another similar environment variable, ENDLIBPATH. As far as I
remember, these two are the only tricky ones.

I hope I provided enough details, but feel free to ask if you need more.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

View raw message