ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran" <stev...@iseran.com>
Subject Re: [Bug 368] Changed - Case sensivity BugRat Report#656
Date Fri, 02 Feb 2001 01:14:22 GMT

----- Original Message -----
From: "Nico Seessle" <Nico.Seessle@epost.de>
To: <ant-dev@jakarta.apache.org>
Sent: Thursday, February 01, 2001 16:16
Subject: Re: [Bug 368] Changed - Case sensivity BugRat Report#656


> ----- Original Message -----
> From: "Conor MacNeill" <conor@cortexebusiness.com.au>
> To: <ant-dev@jakarta.apache.org>
> Sent: Friday, February 02, 2001 12:23 AM
> Subject: RE: [Bug 368] Changed - Case sensivity BugRat Report#656
>
>
> > The only way may be to assume that all file systems are case sensitive
and
> > then populate a set of exceptions according to operating system. Pretty
> > platform dependent, of course.
>
> And what happens if someone mounts a NFS-volume on Windows ? :-)
>
> > Another option would be to make it an optional attribute of the
> > patternset/fileset. This puts control in the user hands and makes any
> > buildfiles that use the attribute somewhat less portable.
> >
>
> Maybe it can simply be handled by using apply, since it is no problem on
> Windows to have all files lowercase one could for example apply an "move
> srcFile tolower(srcFile)" to the files.
>
> Adding (just another) attribute to (to work around windows) would be also
a
> solution. Next question: *Where* do we add it then? It's not specific to
any
> task, so it must be a "magic" (global) property for ant?

Although most of the windows file system is case insensitive, the
illustrious javac is most definately case sensitive -if the case of the java
file does not match that of the classname inside it gets very unhappy. So
anything that adjusts the case of files during a move or copy is a bad
thing.

At the same time, sometimes a case insensitive pattern match may be exactly
what the users want, even on a unix box. So I would propose that
filesets/patternsets do have a 'case insensitive' attribute which controls
how their match takes place. But have the default -even on windows- to be
case sensitive. That way it is much less likely that people developing on
windows will start being case insensitive in their namings of files and
things.

-Steve

(who thinks a case insensitive switch in web server file retrieval on unix
would be kind of handy too)





Mime
View raw message