It took a little longer than planned but this change is being made in
conjunction with activating CI for Java 25.
Projects that depend on WildFly Elytron 2.9.x or later will need to be
using Java 17 as the minimum Java version, Java 11 will not longer be
supported from this point.
On Tue, 18 Nov 2025 at 15:02, Darran Lofthouse <darran.lofthouse(a)jboss.com>
wrote:
FYI Rebecca is currently working on our CI set up for WildFly Elytron
so
we are likely at the point now where we will update the project to target
Java 17.
I will give it a few more days but it is likely the WildFly Elytron
version in WildFly 39 will have dropped support for Java 11. Any projects
that depend upon WildFly Elytron and want to use the later versions will
need to support Java 17 as a minimum.
On Thu, Sep 4, 2025 at 12:42 PM Darran Lofthouse <
darran.lofthouse(a)jboss.com> wrote:
> Now that WildFly Core is built for Java 17 I would like to move WildFly
> Elytron to Java 17 as well from our next releases for WildFly (2.7.x +).
>
> Would this cause any issues for other projects that depend on WildFly
> Elytron?
>
> It should not affect Undertow as we use the Elytron Web project for
> integration, maybe JBoss Remoting but also others with an Elytron
> dependency so let me know if this would be an issue for your project.
>
> --
>
> Darran Lofthouse
>
> Red Hat <
https://www.redhat.com/>
>
> darran.lofthouse(a)jboss.com
> <
https://www.redhat.com/>
>