1969022 - [meta] Deprecate non-toplevel gradle entrypoints

Status: NEW

(Firefox Build System :: Android Studio and Gradle Integration, task)

Description

[Ted Campbell [:tcampbell]]

When Android-Components and Fenix were each independent repositories, we had separate Gradle entrypoints (settings.gradle, etc) and after the monorepo work we now have a mix of things running from top-level and from project directories. Supporting all the things we'd do in subprojects well from the toplevel makes things more consistent with other Firefox development.

Primary criteria for this bug would be to only have the top-level settings.gradle file remaining. There is lots of incremental progress than can be done along the way.

Comment 1

[Nick Alexander :nalexander [he/him]]

For those looking, I see only 4 places that we do gradle -p ...: https://searchfox.org/mozilla-central/search?q=gradle.*-p%5CW&path=&case=true&regexp=true

I expect that a-g-d android-components one isn't necessary now, we can probably run the a-c tasks from top-level. Not sure about the tests.

Comment 2

[Nick Alexander :nalexander [he/him]]

Looks like the TC tasks that use the gradle integration do things like cd to different directories before they run: https://searchfox.org/mozilla-central/search?q=pre-gradlew&path=&case=false&regexp=false

Comment 3

[Ted Campbell [:tcampbell]]

There is also the set of things like Bug 1945245 where locally you need -p to do Fenix non-debug builds (with R8, etc)