Original image by Toby Hudson CC BY-SA 3.0 via Wikipedia
We are pleased to announce the release 1.7.0 of Camel Quarkus! Here are the highlights.
We stand on the shoulders of two giants. Please check the release announcements for Camel 3.8.0 and Quarkus 1.12.0.Final to learn about the news they bring.
The change of default packaging format to Fast JAR in Quarkus 1.12 is worth mentioning also here. Before Camel Quarkus 1.7.0 you used to start your application in JVM mode via something like
$ java -jar target/*-runner.jar
and now since Camel Quarkus 1.7.0, you have to use
$ java -jar target/quarkus-app/quarkus-run.jar
Your Docker files and deployment scripts might need an adjustment when you upgrade to Camel Quarkus 1.7.0.
You can go back to the original behavior by setting quarkus.package.type=legacy-jar in your application.properties.
Camel Quarkus brings support for six new Camel components:
Components newly supported in native mode:
We are following the deprecation of the underlying Camel components:
So far, our AWS SDK v2 extensions were not tested properly. We started adding tests that check their behavior against the real AWS services. Some of the tests can also run against a Localstack mock container.
Camel Quarkus 1.8.0 should appear within a couple of weeks, shortly after Quarkus 1.13.
There is still a lot of Camel components to port to Quarkus. Please upvote your favorites, or even better contribute!