You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add Java 24 compatibility and remove SecurityManager support (bazel-contrib#1719)
Java 24 degrades the SecurityManager into a hollow shell that just
throws exceptions. Later versions will remove the interface entirely.
This commit removes references to the SecurityManager from rules_scala,
which will make tests that call System.exit crash the worker.
It is often possible to edit code to avoid calling System.exit, and guarding
against it requires more effort in Java 24+, likely involving attaching
an agent. Until someone actually has that need, it doesn't seem worth doing.
Bazel is doing the same thing for now, see
bazelbuild/bazel#24354
Add -Dcom.google.testing.junit.runner.shouldInstallTestSecurityManager=false
for junit tests. While recent Bazel versions set this automatically,
older Bazel versions do not, and since we're removing the flag that allows
the SM, we need to set this to prevent crashing for people running older
Bazel versions with Java 17+
Also exclude the .ijwb directory from the buildifier lint check. Failures
due to those files are irritating when running the test locally.
0 commit comments