Hello Wildfly devs,
At my job we want to move to Linux ARM64 machines for our deployments.
The issue we see is that the current (22.0.1) distribution does not include
native binaries for linux-aarch64 architecture :-/
$ find ./ -name "*.so"
I've found https://issues.redhat.com/browse/WFLY-13302 (and
https://issues.apache.org/jira/browse/ARTEMIS-2705) but those are opened
almost an year ago and it is not clear whether they will be resolved any
As far as I understand your recommendation is to build the binaries
locally. This is OK but it adds some extra complexity to the deployment and
Since ARM64 becomes more and more popular for server side deployments I
would like to ask you whether those tickets could be resolved in near
WildFly 23 Beta1 is now available at https://www.wildfly.org/downloads/ !
The biggest news in this release is we now support the Eclipse MicroProfile
4.0 versions of the MicroProfil platform specs. Kabir Khan also added tech
preview support for MicroProfile Reactive Messaging. Lots of other new
The complete list of what went into the main code base is at
while the changes in WildFly Core are at
My deepest thanks to everyone involved in this release. We shortened the
development cycle for this one to get back to a quarterly cycle where we
can release in early September and early December, which I think is best
for avoiding intense work during holiday/vacation periods. The year end
holidays of course also cut into the available development time. But you
all got a LOT done. Great work!
Please give the beta a spin and let us know about any issues you find, as
we work toward a mid-March WildFly 23.0.0.Final.
This mail is for a proposal to provide Helm Charts to build and deploy WildFly applications on OpenShift.
I’ve created https://issues.redhat.com/browse/WFLY-14479 to track this feature request.
As an user, I want to build and deploy WildFly applications on OpenShift using Helm Charts.
The Charts will help users build and deploy WildFly images on OpenShift and leverage the whole features of the application server to make it a best-of-breed runtime on the cloud.
In particular, this chart will let users go from source code to deployed application with an unified and consolidated configuration. They will leverage the most recent innovations of WildFly (Galleon provisioning, Bootable Jar) to make sure that the application matches the user requirements and are fully integrated in the container platform.
This chart depend on WildFly features (S2I, Bootable Jar) and will be regularly updated whenever a new release of WildFly is available so that their users will always be able to use the latest WildFly release.
The proposal PR is at https://github.com/wildfly/wildfly-proposals/pull/377 and a readable version of the proposal is at https://github.com/wildfly/wildfly-proposals/blob/bb62de20d707e013b9db0c0...
Principal Software Engineer