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. 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.

[1]: https://access.redhat.com/articles/1299013#OpenJDK_Lifecycle_Dates_and_RHEL_versions

[2]: https://www.oracle.com/java/technologies/java-se-support-roadmap.html

[3]: https://adoptium.net/support/

James R. Perkins

Principal Software Engineer

Red Hat

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 Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/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/