-
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_disallow_empty_glob fails with local JDK #14646
Comments
The problem is here Line 174 in cb01bde
It's also interesting, because @erikkerber Do you care to reveal what JDK version you're using? It should be located under |
Looks like It might help to clarify I only see this on our CI environment, which uses hosted macOS machines where the configuration ownership is one step away from my team. |
@Wyverald Could this get in 5.0.1? |
@bazel-io fork 5.1 |
Fixes bazelbuild#14646 Closes bazelbuild#14687. PiperOrigin-RevId: 426080540 (cherry picked from commit c2ddbd1)
Related bazelbuild/rules_java#101 |
Description of the problem / feature request:
Setting
--incompatible_disallow_empty_glob
fails on an empty blob in the local_jdk BAZEL.build file:Feature requests: what underlying problem are you trying to solve with this feature?
Use
--incompatible_disallow_empty_glob
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
I believe have a local JDK installed and attempt to build with
--incompatible_disallow_empty_glob
What operating system are you running Bazel on?
macOS 15.2
What's the output of
bazel info release
?If
bazel info release
returns "development version" or "(@non-git)", tell us how you built Bazel.N/A
What's the output of
git remote get-url origin ; git rev-parse master ; git rev-parse HEAD
?N/A
Have you found anything relevant by searching the web?
I have not
Any other information, logs, or outputs that you want to share?
The text was updated successfully, but these errors were encountered: