-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Currently we're using Wildfly 26.1.3. We should upgrade to latest as it's been a minute. See: https://www.wildfly.org/downloads/
Note: This is not a trivial task despite appearing as such on the surface. There are about a dozen apps (different GitHub repos) that rely on Wildfly that are generally all upgraded in lock-step. Also, last time we upgraded from Wildfly 16 to 26 most apps required major changes. For example last time the authentication code built into Wildfly was totally different (and broken, requiring custom code). This time around one thing I'm aware of ahead of time is that package names for Java EE are replaced with Jakarta equivalents. So at a minimum basically every source file of every app must change (though mostly search and replace hopefully).
Besides keeping up with latest developments and avoiding falling too far behind, one major benefit of upgrading is to hopefully fix a few Wildfly bugs such as:
- Memory leak on redeploy - Wildfly 26.1.3 redeploy and restart behavior investigation smoothness#18
- Auth code requires patch to redirect correctly - Login always redirects back to home page presenter#3
- Old yum repo no longer exists - Docker build fails, Wildfly base image too old resize#1
Metadata
Metadata
Assignees
Labels
Type
Projects
Status