On Fri, 6 Jun 2025 18:35:53 GMT, Phil Race wrote:
> 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.ac
On Fri, 6 Jun 2025 18:35:53 GMT, Phil Race wrote:
> 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.ac
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 tes
On Fri, 6 Jun 2025 18:35:53 GMT, Phil Race wrote:
> 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.ac
