<headius>
kares[m]: I am cleaning up deprecations and a lot of them are related to the whole JavaClass removal... maybe we can chat about next steps for actually wiping those classes out in 9.5
<headius>
for now I'm going to see about moving these uses into a utility class that can SuppressWarnings and we can just wipe the whole class out when we finally delete this stuff
<headius>
enebo: so a forward-looking question here... on Java 17 and higher we now get warnings about the whole SecurityManager subsystem being deprecated for removal
<headius>
I'm not sure what to do about those
<headius>
we definitely used to have users that used SecurityManager stuff in JRuby but they clearly won't be able to do that at some point in the future
<headius>
there's not a ton of these but they are hard to eliminate unless we just SuppressWarnings again or move them into a utility class like I'm doing with JavaClass/JavaObject stuff
<headius>
I will table this for the moment but there's dozens of references to deprecated security classes
<enebo[m]>
hmm
<enebo[m]>
yeah this includes all the Ola conditionally testing loading of some of core as well
<enebo[m]>
right?
<headius>
I think that is separate but it might raise some of these deprecated exceptions
<headius>
mostly we use it in places we try to emulate some safe level security checks and when we interact with e.g. MBean stuff that raises e.g. AccessControlException
<enebo[m]>
ah well it may be right time to remove all that as well
<enebo[m]>
I would be surprised how much works with that at this point
<headius>
yeah probably not much
genpaku has quit [Read error: Connection reset by peer]
genpaku has joined #jruby
<headius>
kares[m]: another question: why did this get deprecated? There's no docs on replacement and we use it in many places