-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Update java_tools v13.9 / rules_java 7.12.0 #23738
Conversation
@hvadehra could you please take a look at the presubmit errors or is it okay for me to proceed? Thanks! |
I'm afraid the failures look legit, checking. |
The check was already enforced but `v2.27.0` onwards contains google/error-prone@c2a1a7c which additionally enabled it for primitives Unblocks #23738 PiperOrigin-RevId: 678653085 Change-Id: I16e8068147402c890acebb9c450f1c10676a92a0
@iancha1992 Should be fixed with e89d5cf, please sync this PR to HEAD. |
43844be
to
c0ba713
Compare
I see the same failures in the scheduled build on master, so I think it's okay to proceed. |
e4dbcc6
to
6bba570
Compare
@hvadehra could you please take a look at the presubmits? Thanks! |
I'm seeing this locally which seems relevant to the failures:
|
What changed in rules_java? |
Only relevant bit might be adding a dependency on stardoc which is pulling in rules_jvm_external |
Can we turn that into a dev_dependency so that it doesn't propagate to dependent? |
Context: bazelbuild/bazel#23738 (comment) PiperOrigin-RevId: 680499660 Change-Id: If2f44149382e7205c47a684eb1cb1abadff5a918
Thanks Yun! That seems to have done it. @iancha1992 A test also needed fixing, so made a fresh PR for this in #23811 |
bazelbuild/java_tools#92