Is anyone aware of significant components we integrate into standard WildFly that have dropped SE 11 support?

This includes components used in one of the feature packs that we support (i.e. via Glow suggestion) for integration into standard WF.

I'm not asking about WildFly Preview, where we know EE 11 doesn't support SE 11 so various APIs or impls may have dropped it in their EE 11 variants.

I believe some or all of Smallrye was planning on dropping SE 11 after their releases to support MP 7 were done.

I've heard a rumor that Keycloak dropped SE 11 support.

On Tue, Sep 17, 2024 at 11: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

--

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/BBS3FPWNTCCAZI3BZPLXEBVPKULAJ3U3/