The fix for JDK-8344235: Revisit SecurityManager usage in java.logging after JEP 486 and JEP 491 integration removed use of AppContext from java/util/logging/LogManager.java. That was the only place in the JDK that used jdk.internal.access.JavaAWTAccess.java so it can be removed.
There are 3 tests that use it (digging into internals) but those tests are pointless now that LogManager doesn't use AppContext, so they should be deleted. Automated client tests and logging tests (JDK tier1 for the latter it seems) all pass. ------------- Commit messages: - 8358731 Changes: https://git.openjdk.org/jdk/pull/25677/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=25677&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8358731 Stats: 1110 lines in 6 files changed: 0 ins; 1110 del; 0 mod Patch: https://git.openjdk.org/jdk/pull/25677.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/25677/head:pull/25677 PR: https://git.openjdk.org/jdk/pull/25677
