January 2026 - wildfly-dev - Jboss List Archives

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

by thofman＠redhat.com

6 months, 1 week

1
0
0 / 0

Possible component upgrades report - wildfly-core:main

by thofman＠redhat.com

6 months, 1 week

1
0
0 / 0

WildFly Community Call - 2026-01-08

by Jean-Frederic Mesnil

Hi, we held a WildFly Community call on Thursday, November 13th. Recording can be watched at https://youtu.be/d0k4GL3zQ4g As a reminder this call is open to any community members -- users and developers alike (the meetings are in our WildFly calendar at https://www.wildfly.org/events/#calendar Please find below the agenda of the call: Week 02 (2026-01-08) Happy New Year 🎉 Agenda (:00) * [Brian] WildFly 39 release status * Scheduled for Thu Jan 15 (next week) * We have five blockers but they seem to be in hand * Clustering testsuite hot rod connection failures on SE25<https://issues.redhat.com/browse/WFLY-21314> * This is intermittent and seems to be about starting a remote Infinispan, not WF itself, so we can likely reduce it to Critical and defer, if needed * Clustering topology issue<https://issues.redhat.com/browse/WFLY-21236>, but we have a workaround if need be * Undertow release -- WIP * WildFly Galleon Plugins release<https://issues.redhat.com/browse/WFLY-21284> -- will happen once WildFly Core is released * JBoss Metadata release<https://issues.redhat.com/browse/WFLY-21112> -- WIP; discussion here<https://wildfly.zulipchat.com/#narrow/channel/174184-wildfly-developers/t...> * Nightly CI results are acceptable, except perhaps the Clustering hot rod issue mentioned above * TCK results look good. * [Brian] Move WildFly Core to direct deploy to Maven Central? * Note: we can likely defer this discussion or drop it as the JBoss Nexus issues we had in Dec seem to be better now * With WF 39 Beta we learned that there is a basic element of "staging" when deploying directly. You upload content and then release it. It's not a "staging repo" that maven consumers can access to test your release, but it does allow basic sanity checking and avoiding half-way releases. * A basic issue with deploying directly is getting needed perms; we have established mechanisms for controlling perms via JBoss Nexus. * [Brian] I did some initial work on setting things up for a separate wildfly-ee-10 FP * WIP is at https://github.com/bstansberry/wildfly/tree/legacy-fp * Will need a WildFly feature issue and proposal * basically creates a new FP structure + ee-build / ee-dist, does some initial TS setup stuff * TODO * user boms * full build + dist (i.e. wildfly-ee-10 + wildfly) * complete TS integration * Doc/downloads (using a different archive to stay on Jakarta EE 10) * Uses "ee-10" as a segment of the artifactId of the user-relevant artifacts (e.g. the FP itself, the channel, user boms etc). This will need to change over time, e.g. if we do an EE 11 one once standard WildFly moves to EE 12. * Other "internal" artifacts use "legacy-ee" so they will not need to change. * Status of Java 25 support for WildFly * WildFly Component SE 25 Support<https://docs.google.com/spreadsheets/d/1Un8Q1suq2Y8Aqa490p5EHr3rLtgSKc5pM...> * FYI about interesting discussions * Hibernate ORM 6.6 update to allow bytecode enhancement with SE 25<https://wildfly.zulipchat.com/#narrow/channel/174184-wildfly-developers/t...> * Link to a zulip, wildfly-dev, google group etc discussion End of meeting (:33) ________________________________ -- Jeff Mesnil Software Engineer Red Hat JBoss EAP http://jmesnil.net/ IBM Unless otherwise stated above: Compagnie IBM France Siège Social : 17, avenue de l'Europe, 92275 Bois-Colombes Cedex RCS Nanterre 552 118 465 Forme Sociale : S.A.S. Capital Social : 664 614 175,50 € SIRET : 552 118 465 03644 - Code NAF 6203Z

6 months, 1 week

1
0
0 / 0

Request for a feature team -- WFLY-21109 – Proposal: Add user credentials in a separate directory

by Rafael Rosa

Hi all, As described in the issue WFLY-21109, we need to improve the user experience for creating user credentials (application and management) for cloud deployments. The proposal introduces an enhancement to the add-user.sh script, allowing user credentials to be created outside the server directory and injected into deployments as a secret. We are looking for someone from the security team to act as the SME for this feature. Pedro Silva will provide the outside perspective. If anyone is interested in helping with the review, it would be greatly appreciated. Relevant links: - Jira issue: https://issues.redhat.com/browse/WFLY-21109 - Feature proposal: https://github.com/wildfly/wildfly-proposals/issues/776 Thanks, Rafael Rosa

6 months, 1 week

1
0
0 / 0

Possible component upgrades report - wildfly:main

by thofman＠redhat.com

6 months, 2 weeks

1
0
0 / 0

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

by thofman＠redhat.com

6 months, 2 weeks

1
0
0 / 0

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

by thofman＠redhat.com

6 months, 2 weeks

1
0
0 / 0

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

by thofman＠redhat.com

6 months, 2 weeks

1
0
0 / 0

Possible component upgrades report - wildfly-core:main

by thofman＠redhat.com

6 months, 2 weeks

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

wildfly-dev January 2026