Niklas Gustavsson wrote:
Yeah, this should be pretty straight-forward to make an configurable
option. Of course, it will be crucial that the underlaying file system
doesn't differentiate between files based on the casing. So, this change
wouldn't work all that great on Unix/Linux file systems, but it should
work just fine on Windows.
We currently have no unit tests for the file system code so I'm a bit
reluctant to make the change before I've fixed that. Give me a day or
two and I might have something working.
This has now been implemented. To enable it set the following
configuration property:
config.file-system-manager.case-insensitive=true
or the corresponding XML.
This will affect any case where we try to locate a file or directory.
Listings and creation of objects will work as before. For example, if
you create a directory called "DiR" that exact casing will be used when
creating the file. This means that on a case-sensitive file system, running:
MKDIR DiR
MKDIR DIR
will create two separate directories. Please get back to me if this is
not the desired behavior.
/niklas
