Jin
This is unfortunately still an issue. For local development, I'd just comment out either page from redirects.bzl.
The original idea that @dkelmer and I discussed when forming this codelab was to have the repo be empty by default for teaching purposes. I believe there are also codelab...
I'll assign myself to this because the problem space (side effects of plugin application) is similar to what we did for Firebase, and doing now for Crashlytics in https://github.com/bazelbuild/bazel/issues/7159. It's...
Unassigning myself because I don't have the bandwidth to work on this for the moment.
@cgruber right, makes sense. I'll move this over to rules_android.
@jongerrish ResourceProcessorBusyBox and a few other Android tooling are decoupled from the Bazel binary, in the `@android_tools` repo. To run with a local copy of the `@android_tools` repo, run: ```...
@jongerrish That's a great result! I'll let @djwhang @timpeut and @donaldchai decide what's the best step to take here (I don't work on the Android rules anymore)
cc @ahumesky afaik databinding does not work with bazel yet.
I have a patch that does essentially the same thing. Can we merge this now, and fix the nit later?
Android (AOSP) has a virtual monorepo structure like this: ``` % tree . ├── external │ ├── a │ │ ├── BUILD │ │ ├── LICENSE │ │ ├── METADATA...