Many of the security manager methods will be deprecated for removal in JDK 17 as part of JEP 411, JDK-8264713. Once this JEP is integrated, anyone using JDK 17 to build JavaFX will see '[removal]' warnings from the compiler.
You can use "gradle -PLINT=removal" to generate a list of these warnings.
We will build JavaFX using JDK 16 until after JDK 17 ships (so we won't switch until JavaFX 18), so this isn't urgent, but we should consider doing this for JavaFX 17 so we can test later builds of JavaFX 17 with JDK 17 without seeing the warning.
You can use "gradle -PLINT=removal" to generate a list of these warnings.
We will build JavaFX using JDK 16 until after JDK 17 ships (so we won't switch until JavaFX 18), so this isn't urgent, but we should consider doing this for JavaFX 17 so we can test later builds of JavaFX 17 with JDK 17 without seeing the warning.
- relates to
-
JDK-8264140 Add -Djava.security.manager=allow to JavaFX tests calling setSecurityManager
- Resolved
-
JDK-8264137 Suppress deprecation and removal warnings of internal methods
- Resolved
-
JDK-8269424 Some SuppressWarnings annotations can be more localized
- Resolved
-
JDK-8264713 JEP 411: Deprecate the Security Manager for Removal
- Closed
(1 links to)