Java framework Quarkus 1.0.0.Final touches down
After two release candidates and 30 releases over 36 weeks – that’s one every nine days – the final version of Quarkus 1.0 is here. Don’t feel sad though, the pace won’t slow down and they’re already talking about their plans for Quarkus 1.1! Let’s take a closer look.
We recently wrote about Quarkus 1.0.0 being released, which was big news because of the huge landmark that 1.0 represents for the Java framework. Today, the final version of Quarkus 1.0 has been released, signifying a huge achievement by those involved in its development. And in case you’re not sure about that statement, just take a look at the list of thank-yous in the release notes.
From the very start, Quarkus was envisioned as something small and fast; not just because it can be used for microservices, but also because of its release cadence. We’ve had a release every 1-2 weeks since the project got started, and the contributors have been adamant about keeping the nippy, lightweight approach at the forefront of what they do. In an interview with Red Hat’s Alex Soto earlier this year, he told us that every version of Quarkus is taken care of in a way that it’s production ready, so while 1.0.0.Final might seem to us like a pretty big milestone for the project, it’s pretty much just another day in paradise for the team.
What’s new in Quarkus 1.0.0.Final?
Since there have been two release candidates, 1.0.0.Final is mostly comprised of smaller fixes and improvements to the developer experience and documentation. Over the course of the two release candidates, changes have been made to improve the security and Spring compatibility layers, as well as some others, which I have summarized below.
SEE ALSO: Java Particle Acceleration using Quarkus
When using code.quarkus.io, the generated project now includes a Platform BOM (previously it included a Quarkus BOM). This mostly means users can use the full Quarkus ecosystem, not just the core extensions.
Fixes and upgrades
A number of issues with Gradle integration and the Kotlin extension have been fixed – though it seems to remain an area in need of attention as they make a call for contributions in this area. Some issues with the documentation about using Gmail have been ironed out, and SmallRye OpenAPI and Swagger UI have been upgraded to fix a number of bugs the community found.
Finally, following reports of people being unable to inject
HttpServletRequest in their JAX-RS resources because Vert.x became the default, RESTEasy now has a common ground
HttpRequest class that can be used with the Vert.x layer or with Undertow/Servlet.
What’s next for Quarkus?
As for the future, the pace won’t be slowing down. In the release notes, there is already a comment that support for the just-released GraalVM 19.3.0 is planned for Quarkus 1.1. They also note that using the framework might trigger some unrecommended dependency warnings when using Gradle – these will also be fixed soon. And let’s not forget what they said in the 1.0 announcement: “Don’t expect a slowdown in feature releases. We have a rock-solid foundation now and tons of ideas to deliver.”