-
-
Notifications
You must be signed in to change notification settings - Fork 256
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
cannot load '@rules_jvm_external~5.2~maven~maven//:compat.bzl': no such file #910
Comments
This unfortunately does this fix bazel-contrib/rules_jvm_external#910 which is being encountered on enola-dev#161.
This unfortunately does this fix bazel-contrib/rules_jvm_external#910 which is being encountered on #161.
@shs96c friendly ping - do you have any idea what could be causing this? |
In the https://github.com/bazelbuild/rules_jvm_external/tree/master/examples/simple, the https://github.com/bazelbuild/rules_jvm_external#repository-aliases works as documented. So this problem is specific to my project (above). I suspect that
where as in my project it fails as:
I don't quite understand what defines the In my project there is a bit of a mix of a |
That was it! enola-dev/enola#387 temporarily worked around this (ugly, but it works; I will look into a cleaner solution later), and enabled enola-dev/enola#388 and enola-dev/enola#389 and enola-dev/enola#161 and enola-dev/enola#390 (#NOK). |
enola-dev/enola#161 is a PR which upgrades Bazel from 6.1.2 to 6.2.0.
That upgrades causes the following build failure, which did not occur before the upgrade:
I looked into this a bit, and gather that this may or may not have something to do with #880 from @shs96c which was reviewed by @cheister which is mentioned on https://github.com/bazelbuild/rules_jvm_external/releases/tag/5.2?
I indeed cannot find a
compat.bzl
in this repo, but there are example referencing it, incl. https://github.com/bazelbuild/rules_jvm_external#repository-aliases (and there is acompat_repository.bzl
(which doesn't seem to have moved in a while).My
WORKSPACE.bazel
looks like the example on the README.What am I missing?
The text was updated successfully, but these errors were encountered: