8342992: Security manager check should not use deprecated methods

[kevinrushforth]

As specified in the security manager removal CSR, JDK-8341858, JavaFX now checks at startup whether the security manager is enabled and fails fast with an UnsupportedOperationException if it is. The check is currently done in the <clinit> methods of PlatformImpl and LauncherImpl by calling the deprecated System::getSecurityManager method.

This PR creates a new SecurityUtility::checkSecurityManager utility method in javafx.base that uses reflection to avoid calling API that is deprecated for removal. I also added a call to checkSecurityManager in ReflectUtil and MethodUtil in javafx.base for non-graphical applications that only use javafx.base.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8342992: Security manager check should not use deprecated methods (Bug - P3)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jfx.git pull/1627/head:pull/1627
$ git checkout pull/1627

Update a local copy of the PR:
$ git checkout pull/1627
$ git pull https://git.openjdk.org/jfx.git pull/1627/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 1627

View PR using the GUI difftool:
$ git pr show -t 1627

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jfx/pull/1627.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back kcr! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

[mlbridge]

Webrevs

• 00: Full (6e905c17)