December 2025 - wildfly-dev - Jboss List Archives

by Brian Stansberry

WildFly 39.0.0.Beta1 is now available in Maven Central and on https://www.wildfly.org/downloads/. The release announcement is at https://www.wildfly.org/news/2025/12/19/New-WildFly-39-Beta-release/. I'm very happy with the progress during this release cycle. There's been a real explosion of activity in the last month, some of which is delivered in 39 Beta, some of which progress for things that will be in WF 40, some of which is more long term but very exciting. It's great to see and makes me optimistic for a great 2026 for WildFly. A more technical note is that for 39 Beta we switched to deploying the main AS content (i.e. the https://github.com/wildfly/wildfly build output) directly to Maven Central instead of deploying to JBoss Nexus. This was literally a final day switch, at the end of a multi-day saga. This change should be transparent to end users and to developers in the WildFly ecosystem, but if for some reason it's not please be sure to let us know! Many thanks to Darran Lofthouse who coordinates our beta releases and did a great job dealing with the sudden explosion of activity and then with remaining calm during the multi-day release saga. The December beta is one where we want it to be relaxed so people can slow down for year end, but it never seems to work out that way! Kudos for Rado Husar and Paul Ferraro who were both one of the sources of the explosion of activity and were very helpful in keeping things on track. Finally, thank you to James Perkins, who was very active throughout and who stepped up in a big way at the end to engineer the transition to deploying to Maven Central, and then took on the responsibility for building and deploying the appserver. For those of you who are taking a break this month (and those who aren't!), please enjoy! We'll see you in 2026. Best regards, Brian Stansberry WildFly project lead He/him/his

2 weeks, 4 days

1
0
0 / 0

Possible component upgrades report - wildfly:main

by thofman＠redhat.com

2 weeks, 6 days

1
0
0 / 0

Possible component upgrades report - wildfly-elytron:1.x

by thofman＠redhat.com

3 weeks, 1 day

1
0
0 / 0

Possible component upgrades report - elytron-web:4.x

by thofman＠redhat.com

3 weeks, 2 days

1
0
0 / 0

Possible component upgrades report - wildfly-elytron:2.x

by thofman＠redhat.com

3 weeks, 2 days

1
0
0 / 0

Possible component upgrades report - wildfly-core:main

by thofman＠redhat.com

3 weeks, 3 days

1
0
0 / 0

Possible component upgrades report - wildfly:main

by thofman＠redhat.com

3 weeks, 4 days

2
1
0 / 0

[proposal] WFLY-20918 Add idle time-based eviction configuration for distributable HttpSessions, SFSBs, EJB Timers

by Radoslav Husar

Hi everyone, Last month I submitted a proposal to add idle time-based eviction configuration for distributable HttpSessions, SFSBs, EJB Timers and it is available at https://github.com/wildfly/wildfly-proposals/pull/766 This proposal addresses https://issues.redhat.com/browse/WFLY-20918 for which the user story is: as a WildFly administrator, I want to configure eviction based on idle time rather than just cache size, so that I can better manage memory usage when my sessions and beans have highly variable sizes. The implementation will be available in the coming hours and is targeting WF 39 at community-level stability. I encourage people to review the analysis document and provide any feedback or comments. Thanks! Cheers, Rado

4 weeks

1
0
0 / 0

[wildfly-dev][proposal] WFLY-20091 Provide distributed depoyment repository functionality

by Richard Achmatowicz

Hello All A proposal is now available which introduces an enhanced deployment repository implementation for Wildfly. The proposal document is here: https://github.com/wildfly/wildfly-proposals/pull/771 Brief Summary: This proposal addresses the issue https://issues.redhat.com/browse/WFLY-20091 and its purpose is to provide cluster-wide module deployment information for EJB clients at each module availability update. This feature will generally improve discovery for EJB client applications by providing more comprehensive information on where modules are deployed in a cluster, but is critical for allowing the EJB client to discover module deployments behind a load balancer when using EJB/HTTP. People are encouraged to review the analysis document and provide any feedback or comments on the PR. Thanks! Richard

4 weeks, 1 day

1
0
0 / 0

Possible component upgrades report - wildfly-elytron:1.x

by thofman＠redhat.com

4 weeks, 1 day

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

wildfly-dev December 2025