Quarkus 3.0.0.Alpha1 released - First iteration of our Jakarta EE 10 stream
source link: https://quarkus.io/blog/quarkus-3-0-0-alpha1-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.
Quarkus 3.0.0.Alpha1 released - First iteration of our Jakarta EE 10 stream
By Guillaume Smet
Last week, Max Andersen explained our plans for Quarkus 3 and Jakarta EE 10.
I published yesterday a more detailed blog post explaining how we are building the Quarkus 3 stream.
It is now time to announce Quarkus 3.0.0.Alpha1 which is the first iteration of our Quarkus 3 stream.
A few key points about Quarkus 3.0.0.Alpha1:
-
It is based on Quarkus 2.13.3.Final so it has all the features of this version.
-
It targets Jakarta EE 10, except for JPA, where we are still aiming at EE 9. Thus we are still using Hibernate ORM 5.6.
From the key targets we have for Quarkus 3, some are not there yet:
-
Eclipse MicroProfile 6 - it is not even released so no surprise there
-
Switch to the Flow API instead of Reactive Streams - it is a work in progress
-
As mentioned previously, Hibernate ORM 6
A few things are not working yet, due to upstream issues:
-
REST Assured only works with Jackson, not with JSON-B, as there is no versions of REST Assured supporting the
jakarta.*packages.
Alpha?
We named this version Alpha1 because it is still a work in progress but it doesn’t contain any experimental stuff.
It is a very stable 2.13.3.Final converted to Jakarta EE 10 with some minor additions.
As a result, it should already be very usable.
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