-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
--incompatible_load_java_rules_from_bzl breaks some bazel_tools BUILD files #10839
Comments
Fixes #97 Progress toward google/flogger#122 I have also tested this against Flogger and Dagger (modified to fix their own --incompatible_load_java_rules_from_bzl problems). Everything appears to work except for Dagger, which has some breakages from bazel_tools itself, for which I have filed bazelbuild/bazel#10839. (This is in addition to filing and working around bazelbuild/bazel#10838.) It also includes an upgrade to rules_kotlin to contain the analogous fix for that repo: bazelbuild/rules_kotlin@186c1e1 And ditto for protobuf. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=296727595
Fixes #97 Progress toward google/flogger#122 I have also tested this against Flogger and Dagger (modified to fix their own --incompatible_load_java_rules_from_bzl problems). Everything appears to work except for Dagger, which has some breakages from bazel_tools itself, for which I have filed bazelbuild/bazel#10839. (This is in addition to filing and working around bazelbuild/bazel#10838.) It also includes an upgrade to rules_kotlin to contain the analogous fix for that repo: bazelbuild/rules_kotlin@186c1e1 And ditto for protobuf. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=296727595
I started looking at this, and I'm confused. (First, I should have mentioned that I'm testing with Bazel 2.1.1.) I see changes to add
(tools/android/BUILD is still missing But I don't see the I would have assumed that create_embedded_tools packages the current contents of |
Err, sorry, the current version of tools/android/BUILD no longer uses It's sounding like this is "fixed" by a4de484 and whichever commit removed the |
Sorry for missing these in CL 297608393. (But note that, even after this CL, there is still a breakage when building Dagger with --incompatible_load_java_rules_from_bzl. I'm trying to get to the bottom of it in bazelbuild/bazel#10839.) ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=297822279
Sorry for missing these in CL 297608393. (But note that, even after this CL, there is still a breakage when building Dagger with --incompatible_load_java_rules_from_bzl. I'm trying to get to the bottom of it in bazelbuild/bazel#10839.) ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=297822279
Here's specifically what I'm seeing in case there's something weird about my environment or project:
Note that there are additional errors from running without an Android SDK. But even when I run with the SDK present (at which point the other errors go away), the |
(I thought perhaps that switching to rules_android would help, but it appears not, assuming that I got it right.) |
I tried with 2.2.0 and on another machine, and the build still fails. |
Also failing with 3.0.0. |
Ditto 3.1.0. |
I'm still seeing some errors with 3.3.1. Testing against google/dagger@f3ff00a (which has some other errors related to
|
cc/ @meteorcloudy - because they have lots of recent experience with third party things. I finally caught a detail in the first entry "ERROR: .../external/bazel_tools/tools/android/BUILD:261:1: in java_binary rule @bazel_tools//tools/android:dexer" Since it is in bazel_tools, it may be that we need to update an upstream dependency to get there. This might be a build & packaging problem more than a java rules problem. |
Sorry, the incompatible change is not currently owned by anyone. I'll take a look as soon as I have some free time. |
I think this is expected, but FYI, I do still see this with 3.4.1:
|
This is obsolete; We gave up on |
Similar issues about other files that are currently open:
The text was updated successfully, but these errors were encountered: