Apache Camel Quarkus 1.1.0 has been released!
We continue to integrate with the latest Camel and Quarkus releases, whilst adding new features and fixing bugs.
For a full overview of the changes see the 1.1.0 milestone details.
Here are some of the highlights.
Major component upgrades
- Camel 3.5.0
- Quarkus 1.8.0
We added a whopping 174 new extensions in this release! This is because Camel Quarkus will shortly become the only and default runtime in our sibling project Camel K. 159 of the new extensions initially have support for JVM mode only.
In addition, native support has been added to the following 16 extensions:
- AWS 2 Lambda
- AWS 2 Security Token Service (STS)
- AWS IAM
- SmallRye Reactive Messaging
- ThreadPoolFactory Vert.x
- Vert.x HTTP Client
- Vert.x WebSocket
You can browse the full list of supported extensions over at the extensions reference.
Less use of reflection
Over the past months, we have gradually reduced the number of Camel classes that were needlessly required to be registered for reflection. Thanks to Camel 3.5.0, we have been able to eliminate all of these remaining cases and take advantage of the resulting performance boost.
The project has started publishing SNAPSHOT releases from the
master branch (builds with stable Camel & Quarkus releases), the
camel-master branch (builds with the latest Camel SNAPSHOT) and also from the
quarkus-master branch (builds with the latest Quarkus SNAPSHOT). There are more details about this here:
We ❤️ new contributors!
We were happy to welcome as many as four new contributors in this release period. Lukáš improved some of our tests, Zineb and Marcel were brave enough to deliver two native extensions each and Pooja invested her time in improving our documentation. Many thanks for the contributions!
We move onwards towards supporting Camel 3.6.0 and Quarkus 1.9.0. There’s also a large list of extensions that need native support.
We hope you enjoy Camel Quarkus 1.1.0 and we look forward to your feedback and participation!