Description of the problem / feature request:
Replace this line with your answer.
Related: #5411
Both Gradle and Buck have an option to merge all uses-permissions manifest enteries from child libs to the top level final binary manifest. It would be nice if Bazel supported that as well.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
- Have a android_binary target that depends on an android_library target that defines some permissions in it's manifest.
- build the android_binary target and inspect it's final AndroidManifest.xml
Expected the permission from library to be present
Actual it's not present.
What's the output of bazel info release?
1.2.1
Any other information, logs, or outputs that you want to share?
btw, there is a current bug in bazel where it actually inherits some permissions from child aar_imports. So if you have android_binary that deps on android_library that deps on aar_import that has permissions -- those permissions will be exported.
Description of the problem / feature request:
Related: #5411
Both Gradle and Buck have an option to merge all uses-permissions manifest enteries from child libs to the top level final binary manifest. It would be nice if Bazel supported that as well.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Expected the permission from library to be present
Actual it's not present.
What's the output of
bazel info release?1.2.1
Any other information, logs, or outputs that you want to share?
btw, there is a current bug in bazel where it actually inherits some permissions from child aar_imports. So if you have android_binary that deps on android_library that deps on aar_import that has permissions -- those permissions will be exported.