Alex Humesky

DexFileSplitter is based on dx, and dx is no more

4

The last version of the build-tools in the Android sdk to include dx was 30.0.3. The last significant tool to use dx is DexFileSplitter, so ~~it should be rewritten to...

Update execute.bzl

6

Make `merge_tool` a private attribute (`"_merge_tool"`), like it says it is in the comments.

Zip artifact labels are used, but zip artifact targets aren't generated in maven BUILD file

1

If an artifact depends on a zip artifact, then rules_jvm_external will generate targets that depend on the zip artifacts by label, but no targets are generated for those zip artifacts...

Improve getting actions from the target under test: 1. Add an keyword "mnemonic" parameter to `analysistest.target_actions()` to filter actions by mnemonic. 2. Add `analysistest.target_action(env, mnemonic=None, output_ending_with=None)` to get a single...

Remove exports_manifest attribute of android_library

2

The exports_manifest attribute of android_library is leftover from an internal migration. It should be removed from android_library and manifests should always be merged up the build graph.

The docs for the Android rules (https://bazel.build/reference/be/android) are derived from the Native rules. The docs should be migrated to derive from the Starlark rules. (In particular, once the native rules...

Migrate Bazel Android Tools from bazel repo to rules_android repo

1

The tools that the Starlark Android rules use reside in the https://github.com/bazelbuild/bazel repo, and should be moved to https://github.com/bazelbuild/rules_android

Delete the native Android Rules

1

Once the Android rules have been fully Starlarkified / open sourced, we can delete the native (i.e. written in Java) Android rules