JDK-8264140 : Add -Djava.security.manager=allow to JavaFX tests calling setSecurityManager
  • Type: Bug
  • Component: javafx
  • Sub-Component: other
  • Affected Version: openjfx17
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2021-03-24
  • Updated: 2022-07-20
  • Resolved: 2021-05-24
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
openjfx17Fixed
Related Reports
Relates :  
JDK-8234175 - Remove obsolete ServiceWithSecurityManagerTest unit test
Relates :  
JDK-8264713 - JEP 411: Deprecate the Security Manager for Removal
Relates :  
JDK-8264139 - Suppress removal warnings for Security Manager methods
Description
The security manager will be deprecated for removal in JDK 17 as part of JEP 411, JDK-8264713. Once this JEP is integrated, the JavaFX tests that set a security manager using System.setSecurityManager will fail when run using JDK 17 unless run with "java -Djava.security.manager=allow".

We will build JavaFX using JDK 16 until after JDK 17 ships (so we won't switch until JavaFX 18), but we need todo this for JavaFX 17 so we can test builds of JavaFX 17 using JDK 17 without having several of the tests fail.
Comments
Changeset: 9507ea41 Author: Kevin Rushforth <kcr@openjdk.org> Date: 2021-05-24 12:07:46 +0000 URL: https://git.openjdk.java.net/jfx/commit/9507ea416a14639ed41e4cfdd87df7c12114078c
24-05-2021