a bunch of new features in the Spring Web integration area
many enhancements, mainly aiming at improving performances
a lot of component upgrades, to pull in the latest / greatest available dependencies
some important bug fixes (including one for a potential memory leak in the Reactor Netty client integration)
In addition to that, RESTEasy 4.4.0.Final is the first version relying directly or indirectly on Jakarta EE API artifacts. We've been replacing all JavaEE API dependencies with the corresponding Jakarta EE 8 ones, while moving to new major versions of JBoss spec API artifacts (now forked from Jakarta EE APIs). This basically followed the same approach we used in WildFly (read more from Brian here, if interested).
The 4.4.0.Final release artifacts are available on Maven Central and JBoss Nexus repositories as usual and the distribution can also be downloaded at https://resteasy.github.io/.
If you look at the download page, you might notice that so far 2019 has been a year rich of RESTEasy releases. We've made 11 new versions available to the community, starting a new major (4.0) and six new minor (3.7, 3.8, 3.9, 4.1, 4.2, 4.3) streams. This was partially because we're trying to avoid including features in micro version releases and we're carefully ensuring that anything that is backported to RESTEasy 3 is fully backward compatible, so that it can be consumed by WildFly. The other reason for the high number of minor releases... is basically that we've got a lot of good quality contributions from the community! Thanks!
As the releases have been somehow unpredictable, I wanted to write down and share a development roadmap, but these days that's quite a difficult task, especially considering that now RESTEasy is looking at both JakartaEE and Microprofile evolution (which is far from being set in stone ;-)), while both WildFly and Quarkus are feeding RESTEasy's requirements tracking list and begging for frequent releases ;-) So I think I'll start with providing some highlights on the areas where the core team is currently willing to focus in the next 12-18 months; clearly I expect the community to influence the actual future of the project.
I foresee multiple contributions and request for enhancements coming from the Quarkus land in the very next future. A few examples of possible improvements would be the support for non-blocking IO on server side and possibly an abstraction layer for the access to annotations, to avoid RESTEasy performing a lot of annotation scanning at runtime.
WildFly integration improvements
In addition to the JakartaEE and MicroProfile efforts mentioned above, we still have a few new features that were planned for previous WildFly releases but haven't been completed yet. I'm thinking about exposing statistics for RESTEasy resources in the WildFly management model and possibly adding a new module for WADL support.
That's it for now, I promise I will try to update you on the plans in the future!