Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request to have child's uses-permissions exported to top level manifest #10628

Closed
nkoroste opened this issue Jan 21, 2020 · 2 comments
Closed
Labels
P2 We'll consider working on this in future. (Assignee optional) stale Issues or PRs that are stale (no activity for 30 days) team-Android Issues for Android team type: feature request

Comments

@nkoroste
Copy link
Contributor

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.

  1. Have a android_binary target that depends on an android_library target that defines some permissions in it's manifest.
  2. 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.

@jin jin added team-Android Issues for Android team untriaged labels Jan 23, 2020
@ahumesky ahumesky added P2 We'll consider working on this in future. (Assignee optional) type: feature request and removed untriaged labels Dec 3, 2020
bazel-io pushed a commit that referenced this issue Apr 5, 2022
Adding support for conditionally merging `uses-permissions`.

#10628
#5411

Closes #13445.

RELNOTES: Enable merging permissions during Android manifest merging with the --merge_android_manifest_permissions flag.
PiperOrigin-RevId: 439613035
ted-xie pushed a commit to ted-xie/bazel that referenced this issue Jul 6, 2022
Adding support for conditionally merging `uses-permissions`.

bazelbuild#10628
bazelbuild#5411

Closes bazelbuild#13445.

RELNOTES: Enable merging permissions during Android manifest merging with the --merge_android_manifest_permissions flag.
PiperOrigin-RevId: 439613035
ted-xie pushed a commit to ted-xie/bazel that referenced this issue Jul 6, 2022
Adding support for conditionally merging `uses-permissions`.

bazelbuild#10628
bazelbuild#5411

Closes bazelbuild#13445.

RELNOTES: Enable merging permissions during Android manifest merging with the --merge_android_manifest_permissions flag.
PiperOrigin-RevId: 439613035
ted-xie pushed a commit to ted-xie/bazel that referenced this issue Jul 6, 2022
Adding support for conditionally merging `uses-permissions`.

bazelbuild#10628
bazelbuild#5411

Closes bazelbuild#13445.

RELNOTES: Enable merging permissions during Android manifest merging with the --merge_android_manifest_permissions flag.
PiperOrigin-RevId: 439613035
ckolli5 pushed a commit that referenced this issue Jul 6, 2022
* Support uses-permission merging in manifest merger

Adding support for conditionally merging `uses-permissions`.

#10628
#5411

Closes #13445.

RELNOTES: Enable merging permissions during Android manifest merging with the --merge_android_manifest_permissions flag.
PiperOrigin-RevId: 439613035

* Make ManifestMergerAction worker compatible

Calling `System#exit` kills the worker during the build. Passing the exception up to the worker should be enough for it to end up in the worker or local execution output.

Closes #14427.

PiperOrigin-RevId: 447808701

* Fix ManifestMergerAction test case on windows

`manifest.toString().replaceFirst("^/", "")` silently fails on windows machines causing `removePermissions` to write to the original test file. This pull request creates a new temp file that `removePermissions` can write the modified manifest to.

Pulling this change out of another PR so that it's easier to merge. Original PR here https://github.com/bazelbuild/bazel/pull/13445/files#r631575251

Closes #13760.

PiperOrigin-RevId: 438643774

Co-authored-by: Ben Lee <[email protected]>
@github-actions
Copy link

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 2+ years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.

@github-actions github-actions bot added the stale Issues or PRs that are stale (no activity for 30 days) label Apr 13, 2023
@github-actions
Copy link

This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please reach out to the triage team (@bazelbuild/triage). Thanks!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 We'll consider working on this in future. (Assignee optional) stale Issues or PRs that are stale (no activity for 30 days) team-Android Issues for Android team type: feature request
Projects
None yet
Development

No branches or pull requests

3 participants