11:49 a.m.
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
5:07 p.m.
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(a)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
5:21 p.m.
Hi Brian,
On Mon, Sep 30, 2024 at 5:08 PM Brian Stansberry <
brian.stansberry(a)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.) 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(a)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(a)lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave(a)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...
8:48 a.m.
On Mon, Sep 30, 2024 at 5:22 PM Ken Wills <kwills(a)redhat.com> wrote:
Hi Brian,
On Mon, Sep 30, 2024 at 5:08 PM Brian Stansberry <
brian.stansberry(a)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?
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(a)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(a)lists.jboss.org
> To unsubscribe send an email to wildfly-dev-leave(a)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...
>
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/Him/His
8:58 a.m.
On Tue, Oct 1, 2024, 08:49 Brian Stansberry <brian.stansberry(a)redhat.com>
wrote:
On Mon, Sep 30, 2024 at 5:22 PM Ken Wills <kwills(a)redhat.com> wrote:
> Hi Brian,
>
> On Mon, Sep 30, 2024 at 5:08 PM Brian Stansberry <
> brian.stansberry(a)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
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(a)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(a)lists.jboss.org
>> To unsubscribe send an email to wildfly-dev-leave(a)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...
>>
>
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/Him/His
10:17 a.m.
On Tue, Oct 1, 2024 at 8:58 AM Ken Wills <kwills(a)redhat.com> wrote:
On Tue, Oct 1, 2024, 08:49 Brian Stansberry <brian.stansberry(a)redhat.com>
wrote:
>
>
> On Mon, Sep 30, 2024 at 5:22 PM Ken Wills <kwills(a)redhat.com> wrote:
>
>> Hi Brian,
>>
>> On Mon, Sep 30, 2024 at 5:08 PM Brian Stansberry <
>> brian.stansberry(a)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(a)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(a)lists.jboss.org
>>> To unsubscribe send an email to wildfly-dev-leave(a)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...
>>>
>>
>
> --
> 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
11:44 a.m.
On Tue, Oct 1, 2024 at 11:18 AM Brian Stansberry <
brian.stansberry(a)redhat.com> wrote:
On Tue, Oct 1, 2024 at 8:58 AM Ken Wills <kwills(a)redhat.com> wrote:
>
>
> On Tue, Oct 1, 2024, 08:49 Brian Stansberry <brian.stansberry(a)redhat.com>
> wrote:
>
>>
>>
>> On Mon, Sep 30, 2024 at 5:22 PM Ken Wills <kwills(a)redhat.com> wrote:
>>
>>> Hi Brian,
>>>
>>> On Mon, Sep 30, 2024 at 5:08 PM Brian Stansberry <
>>> brian.stansberry(a)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.
Right, the elytron-oidc-client tests make use of Keycloak APIs to configure
<https://github.com/wildfly/wildfly/blob/main/testsuite/integration/elytro...
the
realms, clients, users, etc. that are needed by the tests. The Keycloak
server version that gets used when spinning up the image to be used by the
tests can be found here
<https://github.com/wildfly/wildfly/blob/main/testsuite/integration/elytro...
.
Farah
> 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(a)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(a)lists.jboss.org
>>>> To unsubscribe send an email to wildfly-dev-leave(a)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...
>>>>
>>>
>>
>> --
>> 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(a)lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave(a)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...
8:44 p.m.
JBoss Threads will require Java 17 as of version 3.8.0.Final. Also, WildFly
Common 2.0.0+ requires Java 17 due to dependencies.
On Mon, Sep 30, 2024 at 5:08 PM Brian Stansberry <
brian.stansberry(a)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.
On Tue, Sep 17, 2024 at 11:49 AM Brian Stansberry <
brian.stansberry(a)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(a)lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave(a)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...
--
- DML • he/him
6:55 p.m.
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_RH...
[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 <https://www.redhat.com/>
<https://www.redhat.com/>
On Tue, Sep 17, 2024 at 9:49 AM Brian Stansberry <
brian.stansberry(a)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(a)lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave(a)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...
4 p.m.
On Mon, Oct 7, 2024 at 6:56 PM James Perkins <jperkins(a)redhat.com> wrote:
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!
[1]:
https://access.redhat.com/articles/1299013#OpenJDK_Lifecycle_Dates_and_RH...
[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 <https://www.redhat.com/>
<https://www.redhat.com/>
On Tue, Sep 17, 2024 at 9:49 AM Brian Stansberry <
brian.stansberry(a)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(a)lists.jboss.org
> To unsubscribe send an email to wildfly-dev-leave(a)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...
>
_______________________________________________
wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave(a)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...
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/Him/His
44
days inactive
65
days old
9 comments
5 participants
participants (5)
-
Brian Stansberry -
David Lloyd -
Farah Juma -
James Perkins -
Ken Wills