> OK. But for case-insensitive file systems it doesn't matter, right? > The need for this getCanonicalFile()
suppose you are building on Windows a jar file in your build.xml you have <jar destfile="some.jar"> <include="ALPHA/BETA/BETA.XML"/> </jar> the jar file will then contain ALPHA/BETA/BETA.XML and it will make a big difference on UNIX, and it will also make a difference under Windows if you extract the jar in a location where there is no directory called alpha, then the new entry will be really called ALPHA/BETA/BETA.XML Conclusion : if we remove the getCanonicalFile, then we are breaking compatibility of behavior with ant 1.5.3 and earlier. It is possible to do that, and write in WHATSNEW : caution : the case of relative paths in filesets will be determined by the case of the include patterns used to define the fileset. > I don't know for sure. Let me see, yep, behavior on MacOS X using HFS > is the same as on Windows. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
