Quarkus Community Call - 06/01/2026 #51825
cescoffier
started this conversation in
Design Discussions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
Yesterday, we had our regular Quarkus community call. Here is a short summary. You can find the complete minutes (including the recording) here: https://docs.google.com/document/d/1TgFZsuOQo9qZ4CnQII5LHhQVgMC6YsVMs1UJIAJooyM/edit?tab=t.0
Recap:
The primary focus of this call was Java 25 preparedness and the "Integrity by Default" changes coming to the JDK. The team detailed the new infrastructure designed to automatically manage JVM flags (like --add-opens) required for libraries such as Netty, removing the burden from the user. This involves new annotations in SmallRye Commons that allow extensions to declare their native access needs at build time.
We also discussed changes to the build tooling. To support these lifecycle improvements, the Quarkus Maven Plugin must now be declared as a Maven extension. This enables a shared "bootstrapped application" state across Maven mojos and improves test configuration reliability.
On the Native Image front, Karm is working on resolving issues with the Mandrel builder for Java 25. While Quarkus defaults to Java 21, users are encouraged to test with Java 25 (requires Maven 3.9.11) and report any warnings. We also touched on the lack of UBI images for Java 25 and the plan to utilize Fedora images for non-LTS Java versions in the interim.
Finally, a new benchmark comparing Spring and Quarkus performance was shared.
Beta Was this translation helpful? Give feedback.
All reactions