How about: f.getAbsolutePath().equals(f.getCanonicalPath())? Unfortunately, the specified behavior for java.io.File is so vague that I would hesitate to generalize to other VM's, but this seems to work on Sun's Java 1.3.1.
But even if this doesn't work uniformly among VM's, it might be enough to solve the original problem (<available/> vs <uptodate/>), if its VM-specific behavior mirrors the VM-specific behavior of <uptodate/>. -----Original Message----- From: Stefan Bodewig [mailto:[EMAIL PROTECTED]] Sent: Friday, January 18, 2002 8:25 AM To: [EMAIL PROTECTED] Subject: Re: Uptodate and Windows case-insensitive filenames problem? On Fri, 18 Jan 2002, Fabrice Delhoste <[EMAIL PROTECTED]> wrote: > > the Available task does not have a "casesensitive" attribute... <available> creates a Java File object and uses the exists method of it - obviously this one is not case sensitive on Windows. I don't know how to solve this, sorry. Stefan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
