On 30/06/2021 08:19, Bernd Eckenfels wrote:
Hello, sorry for being unpopular, but I just hate it to waste
developer resources,
I realy think this deprecation message should be re-considered, it
broke a lot of things, the amount of work to implement a caching
solution feels like a waste of time and on top of it, there is no
clear replacement strategy published yet.
I would restrict deprication (for removal if you really insist) to
javadoc and not poison stdout/stderr.
The purpose of the warning message is to make it very clear that
applications that call System.setSecurityManager in a running VM will
fail in the future. It is not hugely different to the "Illegal
reflective access" warning that were emitted in JDK 9 to JDK 15. Maybe
you could clarify what you mean by "it broke a lot of things". If you
have something that is sensitive to warnings going to stderr then I
would have expected the "Illegal reflective access" warnings to have
caused a lot more issues.
-Alan.
