One of our nightly CI jobs tests WildFly Preview by building it with SE 8 (the standard) and running the testsuite with SE 15. See https://ci.wildfly.org/viewType.html?buildTypeId=WF_Ee9LinuxJdk15 and the discussion of it at https://wildfly.zulipchat.com/#narrow/stream/174184-wildfly-developers/topic/Testing.20with.20more.20recent.20JDKs. A couple tests fail on that job because JBoss WS is trying to load java.security.acl.Group, which isn't present with SE 14 or later. See
This JIRA is basically a WFLY tracker for a test failure that a
JBWS-4133 fix will resolve.
The failing tests are in UsernameTokenElytronTestCase. The particular failure mode is only visible if
WFLY-14758 is fixed; otherwise the tests fail due to WFLY-14758. But with a fix in place for that they still fail with this relevant logging:
The purpose of that CI job is to help drive progress toward SE 17 support for WildFly. i'm using WildFly Preview because it does not use legacy security, and we know legacy security won't work with SE 14 or later. It uses SE 15 partly because that version was available on the CI server and partly because it's useful to see what fails with 15 before moving on to 16 and 17 which may bring their own issues that mask the problems that come with SE 15.