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

[ Bazel ci] Error name 'aar_import' is not defined with Bazel@HEAD #1172

Open
sgowroji opened this issue May 16, 2024 · 4 comments
Open

[ Bazel ci] Error name 'aar_import' is not defined with Bazel@HEAD #1172

sgowroji opened this issue May 16, 2024 · 4 comments

Comments

@sgowroji
Copy link
Member

sgowroji commented May 16, 2024

CI: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/3858#018f7a6e-1950-49f1-9151-af3cc2389a2e

Platform: Ubuntu

Logs:

ERROR: �[0m/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/d15077c341827e73bf2d88b7f622d6f3/external/maven/BUILD:9:1: name 'aar_import' is not defined (did you mean 'cc_import'?)

Culprit: bazelbuild/bazel@947c72d

Steps:

git clone https://github.com/bazelbuild/rules_kotlin
git reset 42ea2e5539ec52ef93cf29607aa889b7d57ea320  --hard
export USE_BAZEL_VERSION=88a230f4cf28deec1455cb2caed4dc9f81e108c9
bazel test  //app:all 

CC Greenteam @fweikert

@sgowroji
Copy link
Member Author

CC @ahumesky @ted-xie

@restingbull
Copy link
Collaborator

Should be fixed by bazel-contrib/rules_jvm_external#1149

@ahumesky
Copy link
Collaborator

ahumesky commented Aug 7, 2024

bazel-contrib/rules_jvm_external#1149 was just merged

@ahumesky
Copy link
Collaborator

Note that bazel-contrib/rules_jvm_external#1149 was reverted: bazel-contrib/rules_jvm_external#1215 due to accidentally requiring all projects that use rules_jvm_external to use --experimental_google_legacy_api. rules_kotlin might already be using --experimental_google_legacy_api so it might be acceptable to use a version of rules_jvm_external before the revert, but of course then you're stuck with that version until the issue with --experimental_google_legacy_api is resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants