DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32487>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32487





------- Additional Comments From [EMAIL PROTECTED]  2004-12-07 03:54 -------
Peter,

I think one needs to differentiate between case-sensitive FSs and case-aware
FSs. NTFS is case-aware in that it retains the original case whenever possible
(although there is no guarantee that it won't get lost when various tools are
used against a file) and certain tools such as "java" *chooses* to differentiate
between "test" and "Test" but this is not a matter of java actually saying that
the two files differ. The Java specification simply states that the filename
casing must map to the class name casing, which is strictly case-sensitive, so
they choose to enforce that. Why? Because Java is strictly concerned with
portability and Sun wants to ensure that if you transfer these files onto
another operating system they will be guaranteed to work out-of-the-box. The
question we must then ask is, is there a analogous concern for Ant? ... I guess
I will say, yes, there is.

Though I wish to point out that I really only meant that drive-letters should be
handled in a case-insensitive manner and I don't think anyone here (Steve
included) will argue that drive letters are ever case-sensitive under Windows. 

Can we agree to treat '/'-style slashes as equivilent to '\'-style slashes under
win32 as well as case-insensitive drive letters in the path? I think that'll
please Samba, NFS and ClearCase as well.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to