Yun Peng

We need to use the Java runfiles library at https://github.com/bazelbuild/rules_android/blob/5f969078a26aa472638b0c16f6c0e747dbb560f4/src/tools/javatests/com/google/devtools/build/android/sandboxedsdktoolbox/apidescriptors/ExtractApiDescriptorsCommandTest.java#L39-L42

For avoiding bind usages, you can check https://bazel.build/external/migration#bind-targets, my guess is no Bazel change is required.

Oh, unless some Bazel native code is referring to `//external:*`.. /cc @ahumesky @ted-xie

Probably here: https://cs.opensource.google/bazel/bazel/+/master:src/main/java/com/google/devtools/build/lib/bazel/rules/android/AndroidSdkRepositoryRule.java;l=38-45

And https://cs.opensource.google/bazel/bazel/+/master:src/tools/android/java/com/google/devtools/build/android/r8/BUILD;l=55 I believe even before starlarkfying the android build rules, we can just replace those labels to directly pointing to `@bazel_tools`

Very exciting to hear that, thanks for your hard work! Do I understand correctly that if we want to remove all the binds from Bazel's WORKSPACE.bzlmod file, we'll have to...

Yes, I think this makes sense, and should probably be added to https://docs.google.com/document/d/1L1JFgjpZ7SrBinb24DC_5nTIELeYDacikcme-YcA7xs/edit#heading=h.5kq5q3o81vg9

/cc @cushon @comius

@[pmbethe09](https://github.com/pmbethe09) is rules_appengine still being maintained?

ACK, then I'll disable rules_appengine in our downstream for now.