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
As you know, WildFly is providing a Docker image for each release of WildFly from the jboss organization at https://hub.docker.com/r/jboss/wildfly/tags.
However hub.docker.com has recently changes their features and we are no longer able to automate new images whenever we tag our GitHub project at https://github.com/jboss-dockerfiles/wildfly. This is becoming a manual task that only a few people in jboss organization can do.
We are trying to find a new way to deliver these images in a sustainable fashion.
One approach would be to move the Docker images to quay.io which provides the basic features we need to build images from our GitHub repo.
We already have a wildfly organization on Quay.io (that provides our S2I images as well as the WildFly operator): https://quay.io/organization/wildfly
This would affect users that pulls our images as they would have to
Internally, there would be no changes: we would continue to build these Docker images from tags in https://github.com/jboss-dockerfiles/wildfly
The latest release for our Docker image was the 25.0 tag.
A transition would be:
0. Advertise that we will stop delivering images from hub.docker.com. At this point, the jboss/wildfly:latest tag will point to 25.0 and will no longer be in sync with new WildFly releases.
1. Set up the quay.io/wildfly/wildfly repo and push the 25.0 tag to it.
-> users can switch from "jboss/wildfly” to "quay.io/wildfly/wildfly” without any impact for their applications
1.a If we eventually release images for 25.0.x versions, we will push images to both hub.docker and quay.io repositories
2. When we release the next major version of WildFly (WildFly 26), the image will be made available only from "quay.io/wildfly/wildfly” with the 26.0 and latest tag
Does that approach sounds sensible?
Principal Software Engineer
Last July, I started a thread here about ways to get native jakarta
namespace variants of artifacts, which we need for our move to EE 10. One
of the items discussed there was "5) New maven module, transform source and
build". I'm posting here as a kind of status update and tutorial about that
At this point there are 11 maven modules in the WildFly main source tree
that are producing artifacts using the approach described there, and there
are PRs open for at least a couple more. I have filed or soon will file
JIRAs for all the remaining WF main tree's modules that produce
artifacts that WildFly Preview currently is transforming when it provisions
a server, so there will be more coming.
The high level overview of how these work is that a pom-only maven module
is created that corresponds to an existing module that produces an javax
artifact. The new module's pom uses the batavia maven plugin (and
Eclipse Transformer under the covers) to find the source code from the
existing maven module, transform it, and write the transformed output to
the target/ dir of the new module, specifically in the
'generated-resources', 'generated-sources', 'generated-test-resources' and
'generated-test-sources' dirs. That generated source is then associated
with the overall maven execution for the module, and thereafter gets
included as part of the subsequent compile, test, package, install and
deploy goals executed for the module. So, presto we have native jakarta
source available that is then compiled and tested and used to
package/install/deploy binary, source and javadoc jars.
The generated source does not get committed into the git repository. The
git repo only has the pom.
It's a common thing for generated source to be used in an artifact build;
for example it's the technique we use to generate implementation classes
from the XXXLogger interfaces we have for each of our subsystems. What
we're doing here just takes this concept to the max by generating 100% of
the source, including test source.
I'm going to use a PR I sent up yesterday to illustrate how to create one
1) Decide whether the module you want to work on is ready. If you're not
the component lead responsible for the module, ask that lead. To see if a
module is 'ready', look at its compile time dependencies and see if it
still depends on other artifacts for which a native jakarta variant is
needed and doesn't exist yet. Ask here or in zulip if you are not sure!
Things can change quickly, and there also may be some edge cases where
you'd think you need a jakarta namespace dependency but you really don't.
If there are dependencies that are not ready yet, stop and wait until they
are available. Or be prepared for your new module to not build, at which
point you can save your work and wait.
2) Create a new dir under ee-9/source-transform for your new module. If the
module you are transforming isn't directly under the root of the WF source,
then create a matching structure under ee-9/source-transform. For example,
I created ee-9/source-transform/jpa/spi to produce a jakarta.* variant of
3) Copy the pom.xml from an *existing source-transform module* into your
new dir. Easiest is to use one that comes from a dir the same # of levels
below source-transform as your new dir, so a couple relative paths in your
new pom are correct. For my PR I copied over
Don't start with the pom from your source input module. Unless you want to
work out how to adapt it to use the source transformation. :) Granted it's
not rocket science. But it's easier for code reviewers to look at these if
they look like the other ones.
4) Change the artifactId in your new pom to *exactly* match the artifactId
of the module you're transforming, but with "-jakarta" appended:
5) Change the 'name' tag to something appropriate, like
6) Change the 'transformer-input-dir' maven property to point to the root
of the module you are transforming:
This property is used in the batavia maven plugin config in the parent
source-transform dir. Each child module sets the property to point to the
correct input source for that module.
This one small tweak is the only thing you need to deal with to get the
source transformation set up.
7) Configure dependencies.
a) Delete the existing 'dependency' entries in your new pom, as they are
for whatever random file you copied in.
b) Copy over the 'dependency' entries from the pom of the module you are
c) For any entries where your new artifact uses a dependency with a
different groupId:artifactId from the one you're transforming, change the
GA. For example:
EE 8 JTA
became EE 9.1 JTA
Or, in another example
an EE 8 based 'ee' subsystem module dep:
became instead a dep on the new '-jakarta' variant:
d) A nice to have is to separate from the others in the dependency listing
deps where WF Preview is using a different artifact from what standard WF
is using. For example see
This separation helps code reviewers.
8) Tell your new module's parent to include it in the build:
9) The ee-9/pom.xml maintains a dependencyManagement set for all artifacts
that differ in WF Preview from what is in standard WF. These can either be
artifacts whose GA is not used at all in standard WF, or ones where WF
Preview uses a different version. Add your new artifact to this
10) Allow re-use of the module.xml that incorporates this artifact between
standard WF and WF Preview. This is done by modifying the module.xml to add
an expression that the maven-resource-plugin replaces when preparing the
module.xml resource file for use in the FP build:
The added @module.jakarta.suffix@ gets replaced either with an empty string
(standard WF) or "-jakarta" (WF Preview)
11) Add your new artifact as a dependency of ee-9/feature-pack/pom.xml.
This is needed so the wildfly-preview Galleon feature pack can utilize your
12) Tell the wildfly-preview feature-pack build to ignore the no-longer
relevant javax artifact you're replacing. This saves build time, compute
resources and false positives in the build log that make us think your
artifact hasn't been handled yet.
(Note the precise spot to put that 'exclude' may differ, a bit. Ask if this
13) Add an entry for your new artifact in the license.xml file for the
wildfly-preview feature back. Put it in the right alphabetical spot based
on its groupId and artifactId.
14) Do a build and if good, commit and send up a PR! If your input module
had tests, your new module should as well and they should run. If you're
curious, have a look in the new target/generated-xxx dirs to see the
This sounds like a lot, and I suppose it is, but other than step 7) it's
all very simple stuff, mostly things you'd do any time you add a new module
to the WF source tree. Granted I'm practiced at this, but it took me about
half an hour to work up the PR I've been using as an example.
If you're interested in doing one of these, and the component lead
responsible for the input module is agreeable, please go for it and feel
free to ask for help.
 Child modules under
 High level tracker issues for this work are
https://issues.redhat.com/browse/WFLY-15437. I'm filing separate issues for
individual pieces and am linking those to one or the other of these two
shows all artifacts (not just those from the WF source tree) that the
WildFly Galleon plugin was transforming in builds on Oct 14. The rows that
end with '-26.0.0.Beta1-SNAPSHOT.jar' are ones that are produced by WildFly
main itself. I add new tabs to that document weekly to track progress on
reducing the # of artifacts being transformed by the Galleon plugin.
which was produced from a maven module with nothing in it but a pom.
Project Lead, WildFly
I'm very pleased to announce that Farah Juma has joined the group of
contributors who can merge changes to the wildfly/wildfly and
wildfly/wildfly-core repos on GitHub (plus a bunch of other associated
repos in the wildfly GitHub org.)
Farah's been a great WildFly contributor for many years now, actively
contributing in many ways to numerous WildFly subsystems and to the
WildFly Core kernel. Among other things this includes coding, writing and
reviewing feature requirements analyses, and lots of code reviews. She's
currently the WildFly component lead in the security areas and for JSF.
She's also the lead for the Elytron project where she does a great job
fostering a healthy community.
Thanks for all your great work, Farah!
Project Lead, WildFly
For (hopefully) WildFly 26, we're planning on including out-of-the-box
support for Micrometer metrics. We're still discussing all of the various
implications of that, and we'd love to have anyone interested join us. If
you'd like more details, please see my latest blog post here:
Principal Software Engineer
Red Hat JBoss EAP
Ken Wills and I did a bit of organizing of the nightly CI jobs for full
Ken created a new 'Main - Nightly Jobs' subproject for them and moved them
from the root project. Then I renamed most of the jobs. Primarily to
replace use of 'Master' or 'Main' in job titles as that is redundant given
the new subproject name. I replaced that with 'Standard' as the relevant
jobs are tests of standard WF (as opposed to Preview) and aren't the
Bootable jar or Galleon jobs. While I was at it I standardized how we
record in the name the OS and JDK used.
The initial driver for this was to make it easier to set up nightly jobs
for the micro branches (e.g. 25.x) when we create those branches. We can
just copy this subproject, tweak a few settings and it's done.
We'd already created the jobs for 25.x when I did the job renaming exercise
so those don't have the updated names. Which is fine; they'll likely become
dormant in a couple weeks once we're done with 25.0.1.
Project Lead, WildFly