-
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
Use bootclasspath jar in proguard genrule #23067
Conversation
Previously, proguard may attempt to access the Java runtime jmods, which aren't declared as inputs.
@werkt Could you verify that this fixes the issue for you? |
This checks out. Thanks for the speedy fix. CI could use some remote execution, I'll have to check to see if this gets a positive result with bazel-remote or something similar to be embedded. |
@bazel-io fork 7.4.0 |
Previously, proguard may attempt to access the Java runtime jmods, which aren't declared as inputs. Fixes bazelbuild#22787 (comment) Closes bazelbuild#23067. PiperOrigin-RevId: 655470599 Change-Id: I5ff6cd9c32f553fc3d8364ba1b6a4f4e3417418b
Cherry-picks of: * Strip unnecessary Bazel server jar contents (bazelbuild#22787) * Use bootclasspath jar in proguard genrule (bazelbuild#23067) Closes bazelbuild#23707 Closes bazelbuild#23708
The changes in this PR have been included in Bazel 7.4.0 RC1. Please test out the release candidate and report any issues as soon as possible. |
Previously, proguard may attempt to access the Java runtime jmods, which aren't declared as inputs.
Fixes #22787 (comment)