[
https://issues.jboss.org/browse/WFCORE-4532?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-4532:
------------------------------------------
[~dlofthouse] The general goal is that the first WildFly .Final release after a JDK goes
GA will support that JDK. JDK 13 is meant to go GA on Sept 17[1], after the planned WF 18
release, so the target would be WF 19, i.e. late November.
Having a WF .Final work with a JDK RC is there is one available is a nice-to-have. We were
able to do that with WF 16 and JDK 12, but it's just a nice to have, something to go
for if people have bandwidth, something to be happy about in
https://wildfly.org/news/2019/02/27/WildFly16-Final-Released/.
If we shifted the WF 18 schedule a bit such that it went .Final after the JDK 13 GA I
wouldn't ask that we support 13; i.e. the expectation has been 19 and a couple weeks
delay doesn't bring in a major requirement like this.
[1]
http://openjdk.java.net/projects/jdk/13/#Schedule
Investigate new JDK 13 regressions
----------------------------------
Key: WFCORE-4532
URL:
https://issues.jboss.org/browse/WFCORE-4532
Project: WildFly Core
Issue Type: Task
Components: Security
Reporter: Richard Opalka
Assignee: Darran Lofthouse
Priority: Critical
Labels: jdk13
Fix For: 9.0.2.Final
Latest Open JDK 13 Early Access 25 introduced three new regressions in our test suite.
Failing tests are:
wildfly-core/elytron/src/test/java/org/wildfly/extension/elytron/TlsTestCase.java
wildfly-core/testsuite/elytron/src/test/java/org/wildfly/test/integration/elytron/sasl/mgmt/KerberosHttpMgmtSaslTestCase.java
wildfly-core/testsuite/elytron/src/test/java/org/wildfly/test/integration/elytron/sasl/mgmt/KerberosNativeMgmtSaslTestCase.java
Could somebody from our security team have a look what is going on [~darran] ?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)