Update the release announcement to note that we stopped deploying tars#928
Merged
Conversation
|
A preview of this PR is available at https://pr-928-wildfly-org.surge.sh |
rhusar
requested changes
Jul 22, 2026
| * As discussed in the <<new_and_notable>> section, https://quay.io/repository/wildfly/wildfly?tab=info[container images, window=_blank] are available for JDK 21 and 25 on UBI 10 minimal. There is no longer a container image for JDK 17 (the JDK 21 image can safely replace its usage). The latest tag now points to the JDK 25 image. | ||
| * We also added a JDK 25 variant of our https://quay.io/repository/wildfly/wildfly-s2i[S2I builder image, window=_blank] and https://quay.io/repository/wildfly/wildfly-runtime[runtime image, window=_blank], and stopped producing new JDK 17 variants. The existing JDK 17 images can still work with WildFly 41, but they are seriously out-of-date when it comes to security vulnerability patches. Users are strongly encouraged to move to the current images. | ||
| * We https://redhat.atlassian.net/browse/WFLY-22024[deprecated support for the AJP listener, window=_blank] in the `undertow` subsystem. Including the `ajp-listener` in your configuration will result in a WARN message in the log. The AJP listener is deprecated due to its inherent security deficiencies (no encryption, no authentication, CVEs), its inability to support modern protocols (WebSocket, HTTP/2), and protocol stagnation (no development since 2001). Users should migrate to HTTP proxying which offers all the same functionality with proper TLS and mutual authentication support. | ||
| * We have https://redhat.atlassian.net/browse/WFLY-22015[stopped deploying tar.gz files to Maven Central for our pre-built installations, window=_blank] (e.g. `org.wildfly:wildfly-dist`). Maven Central quite reasonably imposes limits on the size of upload bundles used when publishing a release, and the size of the WildFly release bundles was far over the limit, particularly since the introduction of WildFly EE 10 and its pre-built installations . We needed to go on a diet, both to avoid needing to ask for permission to exceed the limit and, more importantly, to avoid placing an unnecessary burden on Maven Central and the people who maintain it. So, we stopped deploying the tar.gz files. The zip artifacts are still available. You can still get tar.gz files from https://wildfly.org/downloads[https://wildfly.org/downloads, window=_blank] or the GitHub release page for a release. |
Member
There was a problem hiding this comment.
Suggested change
| * We have https://redhat.atlassian.net/browse/WFLY-22015[stopped deploying tar.gz files to Maven Central for our pre-built installations, window=_blank] (e.g. `org.wildfly:wildfly-dist`). Maven Central quite reasonably imposes limits on the size of upload bundles used when publishing a release, and the size of the WildFly release bundles was far over the limit, particularly since the introduction of WildFly EE 10 and its pre-built installations . We needed to go on a diet, both to avoid needing to ask for permission to exceed the limit and, more importantly, to avoid placing an unnecessary burden on Maven Central and the people who maintain it. So, we stopped deploying the tar.gz files. The zip artifacts are still available. You can still get tar.gz files from https://wildfly.org/downloads[https://wildfly.org/downloads, window=_blank] or the GitHub release page for a release. | |
| * We have https://redhat.atlassian.net/browse/WFLY-22015[stopped deploying tar.gz files to Maven Central for our pre-built installations, window=_blank] (e.g. `org.wildfly:wildfly-dist`). Maven Central quite reasonably imposes limits on the size of upload bundles used when publishing a release, and the size of the WildFly release bundles was far over the limit, particularly since the introduction of WildFly EE 10 and its pre-built installations. We needed to go on a diet, both to avoid needing to ask for permission to exceed the limit and, more importantly, to avoid placing an unnecessary burden on Maven Central and the people who maintain it. So, we stopped deploying the tar.gz files. The zip artifacts are still available. You can still get tar.gz files from https://wildfly.org/downloads[https://wildfly.org/downloads, window=_blank] or the GitHub release page for a release. |
Member
There was a problem hiding this comment.
Or even consider for brevity:
s/"go on a diet"/"reduce artifact size"
s/"avoid needing to ask for permission to exceed the limit"/"avoid requesting an exemption"
Member
|
Thanks @bstansberry |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#wildfly-developers > Wildfly 41 Preview no tar.gz