On Tue, Oct 1, 2024 at 8:58 AM Ken Wills <kwills@redhat.com> wrote:


On Tue, Oct 1, 2024, 08:49 Brian Stansberry <brian.stansberry@redhat.com> wrote:


On Mon, Sep 30, 2024 at 5:22 PM Ken Wills <kwills@redhat.com> wrote:
Hi Brian,

On Mon, Sep 30, 2024 at 5:08 PM Brian Stansberry <brian.stansberry@redhat.com> wrote:
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.

I just tried updating KeyCloak in Elytron from 25.0.2 to 25.0.6 (and also in WF, https://github.com/wildfly/wildfly/pull/18249). It will no longer compile with JDK 11 and requires 17 at a minimum: https://github.com/wildfly-security/wildfly-elytron/pull/2207/checks (The WF job appears to pass because it is built with JDK 17, then tested with 11.)

Tangent -- that's odd. We have to use 17 to compile the TS but it runs ok with 11?

That appears to be the case, yes. It is not clear if anything in the testsuite is actually running anything that's using it, which may be why the tests pass. I'll take a closer look today 

I believe it's test infrastructure for testsuite/elytron/elytron-oidc-client. It's used to spin up a remote Keycloak for the WF instance to interact with.

But, my recollection is there's an odd mix of versions involved, where maybe what we use client side is different from the Keycloak server. The latter may be older, hence it still supports SE 11.

Ken



The KeyCloak website says JDK 21 is the minimum: https://www.keycloak.org/getting-started/getting-started-zip

Ken
 

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/


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