Open
Description
This isn't an immediate priority, but Gradle has many pitfalls which makes development more challenging:
- There's no control over which resources/manifests are included in the final binary beyond production/test dependencies on modules (which makes creating test modules/libraries more challenging)
- Replacing component implementations (e.g. for test mocks/fakes) is non-trivial with Gradle
- Gradle builds can be a bit slow
- Gradle changes definitions often, so workarounds to any of these problems are likely to break quickly
Bazel allows for more granular control over how dependencies are manged, and in a structured way that will have long-lived support. Bazel includes native support for Android Studio (https://docs.bazel.build/versions/master/bazel-and-android.html) and can support Maven dependencies just like Gradle (https://docs.bazel.build/versions/master/generate-workspace.html).
Metadata
Metadata
Assignees
Labels
Indicates that an issue is too large and should be broken into smaller chunks.Indicates that an issue needs more detail in order to be able to be acted upon.This work item is really important to complete for its milestone, but it can be scoped out.Temporary label for Ben to keep track of issues he's triaged.End user-perceivable enhancements.