On Tue, 15 Oct 2024 15:21:32 GMT, Alan Bateman <al...@openjdk.org> wrote:
>> src/java.logging/share/classes/java/util/logging/LogManager.java line 2430:
>>
>>> 2428: @Deprecated(since="17", forRemoval=true)
>>> 2429: public void checkAccess() {
>>> 2430: throw new SecurityException();
>>
>> Though this method is no longer called in the JDK, this is a change of
>> behaviour that could affect subclasses of `LogManager`, or code using the
>> `LogManager` that might still be calling this method. This method is
>> deprecated for removal, and degrading it to always throw an exception is a
>> logical step prior to removing it. However, I wonder if this shouldn't
>> better be done separately, outside of this JEP?
>
> This is forced move. Same thing with Thread.checkAccess and
> ThreadGroup.checkAccess that also have to be re-specified to throw
> unconditionally. They are called out in the CSR.
OK
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/21498#discussion_r1801445724
