Quarkus 3.0.0.Alpha3 released - Third iteration of our Jakarta EE 10 stream
source link: https://quarkus.io/blog/quarkus-3-0-0-alpha3-released/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Blog Quarkus 3.0.0.Alpha3 released - Third iteration of our Jakarta EE 10 stream
Quarkus 3.0.0.Alpha3 released - Third iteration of our Jakarta EE 10 stream
By Guillaume Smet
As you might know by now, we started a Quarkus 3.0 effort last year and we are continuing this effort, which was described here, here, here, and here.
Quarkus 3.0.0.Alpha3 is the third iteration of this work.
On the Jakarta EE 10 front, it doesn’t bring anything new, except for a few bugfixes and upgrades.
But it comes with some significant changes:
-
This version is based on our current
mainbranch: it contains all the refinements of 2.15.0.Final, 2.15.1.Final, 2.15.2.Final, 2.15.3.Final, and 2.16.0.Final. -
It upgrades Quarkus to Mutiny 2 and the Java Flow API.
-
It simplifies how Kotlin is handled by our classloader, which should ease the work on Kotlin-based Quarkus extensions.
We plan to release the next Alpha in about a month. Until then, we encourage you to test it and report your feedback.
Trying out Quarkus 3
For now the easiest way to get started is using code.quarkus.io or use the Quarkus CLI:
Mind you that at this stage, while all the core extensions are available, only parts of the Quarkus platform is present. Not all extensions have yet migrated to Jakarta packages (e.g. Camel Quarkus or Kogito are not yet available).
Upgrading to Quarkus 3
For existing applications where all extensions are available, we have an early OpenRewrite recipe that you can try.
There is a one-liner that attempts to do it automatically using a JBang script:
For Linux:
For Windows:
You can also do it manually by downloading the OpenRewrite recipe and apply it manually with the following Maven command:
Once this has been run your project should have its dependencies and source code updated to use Quarkus 3.
If it does not work for you, it could be we missed something or you are using extensions not yet supporting Quarkus 3.
Let us know in either case so we can together improve the migration script.
Come Join Us
We value your feedback a lot so please report bugs, ask for improvements… Let’s build something great together!
If you are a Quarkus user or just curious, don’t be shy and join our welcoming community:
-
provide feedback on GitHub;
-
craft some code and push a PR;
-
discuss with us on Zulip and on the mailing list;
-
ask your questions on Stack Overflow.
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK