JodaTime uses java.lang.SecurityManager which is scheduled for deletion

[kluever]

https://github.com/JodaOrg/joda-time/blob/main/src/main/java/org/joda/time/convert/ConverterManager.java uses SecurityManager which is "deprecated and subject to removal in a future release. There is no replacement for the Security Manager. See JEP 411 for discussion and alternatives."

[kluever]

A teammate also said:

I'll note too that its references to java.security.AccessController and java.security.Policy are in the same boat. I imagine if SecurityManager is finally deleted then those will be at the same time.

There are also similar warnings about calls to the constructors of Integer etc.

[jodastephen]

Yes, it is all a lot of fun....

[jodastephen]

If version 3 of Joda-Time is successful, use of the security manager would be removed.

[kluever]

FWIW, we probably don't need to worry about the boxed primitive constructors that I previously mentioned. It sounds like the upstream folks are going to remove the forRemoval bit on those deprecations.

The SecurityManager issue still is a problem though :(