Original image by Toby Hudson CC BY-SA 3.0 via Wikipedia
Why two releases one after another?
Camel Quarkus 1.2.0 was scheduled - with some reasonable time reserve - to be included in the Quarkus Platform release 1.9.0. The next day after we opened the voting, we realized that Camel 3.6.0 is going to be released in the coming days and that it could actually catch Quarkus 1.9.0 too. Therefore we did one more release upgrading to Camel 3.6.0, so that the freshly released Quarkus Platform 1.9.0 contains the newest and greatest Camel.
What’s new
First of all, Camel 3.6.0 alone brings a lot of improvements and optimizations that make Camel Quarkus even faster and more effective than before.
New extensions and extensions newly supporting native mode
There are 10 new extensions:
AWS XRay (JVM only)
HBase (JVM only)
Jasypt (JVM only)
JCache (JVM only)
LRA (JVM only)
Ribbon (JVM only)
Shiro (JVM only)
Spark (JVM only)
And there are 16 promotions from JVM-only to native:
Check the full list of supported extensions in the extensions reference.
With Camel Quarkus 1.3.0, we got very close to supporting all components required by Camel K.
Documentation
Following a request from a user Native since and JVM since versions are now kept in separate columns on our Extensions reference pages
We have added a section about defining Camel routes in XML
We now have a Change log updated by the CI.
What’s next?
We would like to promote more extensions to native. Please upvote your favorites, or even better contribute!
We hope Camel Quarkus 1.3.0 brings some tangible value to you and we look forward to your feedback and participation!