I just noticed that by default, a NamedDomainObjectCollection does allow two objects with the same name with different cases. Not sure if this is a bug or a feature, but as soon as a task uses that name as input/output file/location, it would break consumers with case insensitive file systems...

testing.suites.named("test", JvmTestSuite); testing.suites.create("TEST", JvmTestSuite)

case insensitive file system is the gift that never stops giving. dev life pro tip: you can create a case sensitive volume on your APFS formatted drive with a trivial amount of work so that your projects can live in a sane space.

indeed, that’s the first thing I do with any new Mac - a ‘develop’ case-sensitive filesystem to avoid surprises. Case insensitive filesystems are a mess. https://www.phoronix.com/news/Linus-Torvalds-Anti-Case-Fold

lol I love a good harsh linus rant.

I absolutely agree, but it’s still a footgun because Windows and macOS use a case insensitive file system by default 😐

But nothing Gradle should care about, there are so many footguns with that, like renaming a file name's upper / lower case and committing to Git and on Win and Mac this is no change and then some things that treat the file names case sensitively do not work property.

It you have a class named Foobar besides a class named FooBar

Not like something like that could ever happen in any project you might use ...

Those are two separate projects though :-D