Hello WildFly team,
I work for one of the bigger ARM64 hardware providers.
My client is willing to donate a build server that could be used as a
TeamCity agent to execute the WildFly test suites on ARM64 Linux.
The aim is to make sure that WildFly is running fine on ARM64 architecture
in the long run.
I've ran 'mvn install' on one of our systems and it is passing
If a problem arises in the future on ARM64 then me and my colleagues would
be glad to help with any ARM related issues!
Is this something you would be interested to have ?
We recently ran into an issue because WildFly exports an old version of
Jasypt. We created WFLY-13059 for this .
We would be willing to work on a patch but we need guidance on which
proposed solution you prefer.
I assume everyone is aware of what Wildscribe  is. I've had a thought
that instead of having this massive site that will keep growing with each
version of WildFly released that we start adding this model documentation
on the WildFly Documentation site . The idea is to just add a link on
each releases index page with a link to the model descriptions.
This would be automated as well with the docs project within WildFly. It
means that as part of the release process when building the docs the
Wildscribe model pages would be generated automatically.
My proposal would be for WildFly 19+ we would no longer update the
Wildscribe website. As you can see on the site if you click on versions
it's getting quite long :). All new Wildsribe pages would be present on the
main documentation for that version. The Wildscribe site would have a note
about where the documentation would now be for newer releases.
Any thoughts or concerns about this? If not objections I'll file a JIRA and
do some work on this as it shouldn't take all that long.
James R. Perkins
JBoss by Red Hat