Gradle commands behave strangely with subproject as cwd

Old Forum Archive Bugs
1

In a multiproject, when running gradle commands like gradle shadowJar within a subproject directory as the current working directory, Gradle mistakenly treats the subproject as a root project, and fails to import the parent project’s settings.

In the future, could Gradle please automatically search for parent projects, to prevent this oddity from happening?

2

Gradle does search for a parent project (you have to explicitly disable it with -u). I’m not sure what you mean by “parent project’s settings”. What looks different?