This message was deleted.

Found the problem by total accident... and reported it: https://github.com/gradle/gradle/issues/27379

Interesting. On my Mac have created a case sensitive volume for all development, to tease out these issues, works well.

Well, that's the price you pay for using a case insensitive file system. 😄

In what scenario would someone want

:foo

to implicitly refer to

/Foo

? If that's the actual intention/need, they can still do so by explicitly setting

projectDir

even after my proposal is in place, right?

That is indeed questionable and results in a warning with 8.5 on a case-sensitive file system. But if people are used to case-sensitive file systems and everyone working with the build is working with case-sensitive file system anyway, they might want to have

:foo

in

/foo

and

:Foo

in

/Foo

which would not be possible anymore with your proposal, except it is supported in a way to manually configure this still. I don't think it is a good idea to have such a situation, but this is a typical religious war of whether it is a good idea to have things on filesystem just differing in case. 🙂

:foo

in

/foo

and

:Foo

in

/Foo

, that's a good point, you might want to add it to the issue 🙂