hvadehra
hvadehra
@seaurching the linked/related issues appear to be fixed. Are you still having this problem?
It sounds like you're running into https://github.com/bazelbuild/bazel/issues/7330
The Flogger test needs to be updated. It's been fixed internally (423382085) but for some reason has not been exported to github yet (probably waiting for an error prone release)...
Got it, I'll mail a change to update it locally at desugar as a followup.
Reopened, and transferring to rules_java to track dropping these in the next major version release.
Just a heads up, this is being rolled back, it breaks things internally. But the number of breakages are very small, so it's probably safe to keep for Bazel.
As it turns out, rolling back does not help as it was a bad interaction with https://github.com/bazelbuild/bazel/commit/78971a932bae9d788014df9b6235fb8242b59a77 Rolling it forward, sorry for the noise.
We filter out non-`.java` files from `srcs` and files with the `.properties` extension are specially handled as resources. The problem here seems to be that we create a separate jar...
(moving this to rules_java, as the rules now live there)
See https://github.com/bazelbuild/bazel/issues/20298 for the last time this came up (cc @fmeum ) As a workaround in the meantime, consider using a custom `java_toolchain` that overrides `header_compiler_direct = "@remote_java_tools//:TurbineDirect"`