JBoss.ORG

This Week in JBoss - December, 29th 2022

Happy Holidays!

Welcome to our last installment of JBoss Editorial for 2022! As we are about to let this year behind us, it’s time to look back and review our biggest achievement of the past twelve months, but also look ahead to 2023 and what is as in store for the JBoss community!

In the previous years, it was Mark Little who wrote this last editorial, often sharing his thoughts on the JBoss community accomplishments and the exciting challenges of the next year. Needless to say, I have impossible shoes to fill in for here! So, I’m not even trying to :), especially as I certainly don’t have the same overview that Mark has on our industry. Also, I will not list all of the milestones the JBoss community achieve. There were simply too many of them to do so, from Quarkus reaching its 200th release and its third major version, Wildfly implementing the latest version of the Jakarta EE specification or Keycloak named by GitHub one of the top projects in 2022. The only one I could really discuss is the success of my own personal project, integrating as much as possible the JBoss community famous projects into Ansible (Wildfly, Infinispan, Keycloak, and AMQ), both upstream (with the collection available on Ansible Galaxy) and downstream (on Ansible Automation Hub for Red Hat customers). One of those extensions is now even part, as a technical preview feature, of the latest release of Red Hat JWS! But, once more, this is only one of the numerous achievements of this year.

This short inventory of mine is probably as incomplete as it is biased, but it does make my case: yet again, the JBoss community has been thriving, releasing new version often, and producing quality content (blogs, videos or presentation). I, for one, can’t wait to see what will come out of it next year, and if you are too, well, I have good news. You are already in the right place ;)! The JBoss Editorial will continue and will keep you inform, as much as we can, of everything happening!

That’s all folks! Please join us again in two weeks for another installment of our JBoss editorial!

Romain Pelisse