A late reply as for some reason I thought I already replied :)I think it would be good to move to Java SE 17 as a base. This is the direction Jakarta EE 11 is going and from what I understand the direction that SmallRye would like to go.
Yes, this summer I communicated to Martin Stefanko that, after the implementations for the MP 7.0 specs, the WildFly project would no longer ask SmallRye for SE 11 binaries.
It would likely save us from having to potentially fork any projects that move requirements to a base of Java SE 17.The Java SE 11 full support ends at the end of this month as well, 31 October 2024. At least it does for Red hat builds [1] of OpenJDK. It looks like Oracle Java SE [2] has ended support already, only leaving Eclipse Temurin [3] after this month.
This is a good point. Users of course can opt for longer lasting support for SE 11 from their Java vendors, which Red Hat will provide and it looks like Oracle provides. But WildFly itself uses Red Hat OpenJDK quite a bit in CI.
Between this and the fact that Keycloak has moved to SE 17, leaving us no source for an SE 11 saml adapter, that's enough to say WildFly 34 is the last release that will support SE 11. The other points discussed here are icing on the cake.
I intend to announce that in the WF 34 Final release announcement, and also separately.
That release is in its final stages, so if anyone has any objections, now is the time to speak up!
_______________________________________________On Tue, Sep 17, 2024 at 9:49 AM Brian Stansberry <brian.stansberry@redhat.com> wrote:_______________________________________________WDYT?We've been considering doing this for a long time, and I think it's only a matter of time before important libraries needed for standard WF are only compiled to SE 17.I think WF 35 would be the absolute end of the line for SE 11 support in std WF; after that Jakarta EE and probably our MP impls from smallrye will force a move.But I suspect something could easily happen during the WF 35 dev cycle that forces a move, and I think we'd be better off announcing a plan to move on around the team of WF 34 Beta, and then announcing WF 34 is the end for SE 11 when we release the Final.--Best regards,Brian StansberryPrincipal Architect, Red Hat JBoss EAPWildFly Project LeadHe/Him/His
wildfly-dev mailing list -- wildfly-dev@lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave@lists.jboss.org
Privacy Statement: https://www.redhat.com/en/about/privacy-policy
List Archives: https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message/QQYCEK2BXPNC3CG2QTXMA7B4EVC4YJIF/
wildfly-dev mailing list -- wildfly-dev@lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave@lists.jboss.org
Privacy Statement: https://www.redhat.com/en/about/privacy-policy
List Archives: https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message/UOVX6T7MCWJECGLDYFYR4HDWQISUYSXY/