Rob K.
I recently encountered some strangeness with CYGWIN when trying to set
alternate JAVA_HOME for testing the build of the javadocs target with
different versions of Java.
I did set JAVA_HOME inside of CYGWIN but it didn't do what I expected.
I ultimately got it to work by removing the JAVA_HOME that I was setting
in DOS (before the CYGWIN window even came up).
In Windows, from your control panel you should have a "System" icon, and in
that thing a tab "Advanced" and in there "Environment Variables".
Thats where I killed the setting of JAVA_HOME under Windows. You can check
with the "set" command under a DOS Window.
But then in CYGWIN I had to add it back in, for example:
export JAVA_HOME="D:\\installed\\jdk_ibm1.3.1"
(note that its under CYGWIN but it looks like a DOS variable, and note the
double back-slash pairs)
Then the JAVA_HOME stuck the way I wanted under CYGWIN.
Brian Minchau
XSLT Development, IBM Toronto
e-mail: [EMAIL PROTECTED]
"The voices in your head are so loud that even I can hear them."
