-
-
Notifications
You must be signed in to change notification settings - Fork 255
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
[Bazel CI] Build failed with errors: no native function or rule 'aar_import' #1139
Comments
ahumesky
added a commit
to ahumesky/rules_jvm_external
that referenced
this issue
May 23, 2024
…utomatically if the version of Bazel used does not contain the native version of aar_import. This also updates the version of rules_android to the latest commit, because version 0.1.1 is basically just wrappers around the native versions of the rules. This also disbles `--experimental_sibling_repository_layout` added in bazel-contrib@b6631f9 because the latest rules_android uses protos in go, and there is a problem compiling protos in go with `--experimental_sibling_repository_layout`: bazel-contrib/rules_go#3947 Fixes bazel-contrib#1139.
ahumesky
added a commit
to ahumesky/rules_jvm_external
that referenced
this issue
Jul 9, 2024
…utomatically if the version of Bazel used does not contain the native version of aar_import. This also updates the version of rules_android to the latest commit, because version 0.1.1 is basically just wrappers around the native versions of the rules. This also disbles `--experimental_sibling_repository_layout` added in bazel-contrib@b6631f9 because the latest rules_android uses protos in go, and there is a problem compiling protos in go with `--experimental_sibling_repository_layout`: bazel-contrib/rules_go#3947 Fixes bazel-contrib#1139.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CI: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/3858#018f7a6e-1b58-4ec1-a31d-6067bf5a3da1
Platform: Ubuntu
Logs:
Culprit: bazelbuild/bazel@947c72d
Steps:
CC Greenteam @fweikert
The text was updated successfully, but these errors were encountered: