apache
Add SecurityManagerCompatibility shim
This is a shim to allow the use of both modern (JRE 18+) and legacy APIs (deprecated in 17, degraded in 23, removal unknown) related to JEP 411: Deprecate the Security Manager for Removal.
This shim implements the interim strategy outlined in KIP-1006: Remove SecurityManager Support where legacy APIs are used as long as they are available and functional. Once the legacy APIs are removed or degraded, the modern APIs are used instead.
The shim is structured as a general interface with four 'strategy' implementations for testability. These implementations allow for mocking out the classloading infrastructure to simulate situations which no current JRE implements, namely removal and further degradation of functionality
@vlad-lyutenko the Kudu community doesn't accept code contributions via pull requests, the changes are reviewed and merged via gerrit: https://gerrit.cloudera.org/q/status:open+project:kudu I'd recommend submitting this patch there. Thanks for looking into this!
Hi @vlad-lyutenko, thank you very much for this PR!
As @zchovan mentioned, the Kudu project doesn't merge new code through PRs; we use the gerrit tool to do code review and submission. Could you follow the guidance here to adapt this PR into a gerrit change?
Hi, how is the progress of this work?
Hi! The change has been reviewed and merged: https://gerrit.cloudera.org/#/c/22703/ Merged commit: https://github.com/apache/kudu/commit/586cfc20905df35f49541b53af4442736790b0c1
