Thanks all, for the bug/fix pointers!
-The Wabbit
At 04:20 PM 3/18/2005, you wrote:
--- Martijn Kruithof <[EMAIL PROTECTED]> wrote:
> I recently fixed bug 31245. The problems seem to
> emerge from the way
> cygwin, the jvm, windows and the ant script expect
> the CLASSPATH to be.
> : being the path
--- Martijn Kruithof <[EMAIL PROTECTED]> wrote:
> I recently fixed bug 31245. The problems seem to
> emerge from the way
> cygwin, the jvm, windows and the ant script expect
> the CLASSPATH to be.
> : being the path separator on cygwin and the drive
> letter separation on
> windows gives not s
I recently fixed bug 31245. The problems seem to emerge from the way
cygwin, the jvm, windows and the ant script expect the CLASSPATH to be.
: being the path separator on cygwin and the drive letter separation on
windows gives not so nice effects when paths are normalized using the
utilities of
Remember that both path.separator and java.class.path
are technically VM settings so the only part of Ant
that could be responsible is really the invoking
script. There are always adjustments being made for
cygwin in that script. Things I would try:
remove the trailing semicolon from your CLASSP
Ant Users/Developers,
I noticed some odd Ant behavior on an installation like:
Windows 2K
Cygwin 1.5.10-3 (will use the 'ant' shell script to run Ant)
Bash 2.05b.0(1)-release (i686-pc-cygwin)
Ant 1.6.2
Given a CLASSPATH like:
U:\pkg\ant-1.6.2\lib\ant.jar;U:\pkg\ant-1.6.2\lib\ant-lau
