-
Notifications
You must be signed in to change notification settings - Fork 6
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
UnsupportedOperationException: The Security Manager is deprecated and will be removed in a future release #13
Comments
I believe this is because you are using a JDK version > 11 which is what the build process expects. I will dig up how to override this and report back. We could do a better job of making this more obvious. |
Fixes #13 Signed-off-by: Matt Klein <[email protected]>
Fixes #13 Signed-off-by: Matt Klein <[email protected]>
Thanks for the quick fix @mattklein123 🙇♂️ Confirming that #16 fixes it for
Noting that without the patch from #16 I also want to mention that interestingly, before the patch, I tested it setting Java 11 version explicitly, and the error was still thrown. Tested with
and
and got the same cc @murki |
Thanks let me take a look. |
@pablo-guardiola I think #18 should really fix. :) |
Hey @mattklein123 I tested the changes from #18 and I can confirm both Thanks for the quick turnaround! cc @murki |
I'm trying to build the SDK following the instructions from
README
and examples/README.md and when running$> ./bazelw test //platform/jvm/...
locally most of the tests fail due to 👀Full output
After some digging found out a workaround that worked for me - adding
common --jvmopt=-Djava.security.manager=allow
to the.bazelrc
.Full output
At a first glance, I don't see that
jvm
tests run as part of CI - didn't find any occurrences in.github/workflows
.I can cut a quick PR myself if you're fine with the change. Please let me know ✌️
Refs. bazelbuild/bazel#14502
cc @murki
The text was updated successfully, but these errors were encountered: