We are pleased to announce the release 1.8.0 of Camel Quarkus! Here are the highlights.
Please check the full release announcement of Camel 3.9.0.
The new release of Quarkus brings several new features:
- DevServices simplify testing with containers
- OpenTelemetry is now supported via two new extensions
- Kubernetes Service Binding simplifies the deployment on Kubernetes.
- New MicroProfile REST Client based on RESTEasy Reactive.
- Test coverage reports with
New language DSLs
pom.xml file with the appropriate dependencies in addition to the route definition files. Except for XML and YAML, these DSLs are supported only in JVM mode, because they load and compile the routes at runtime.
Except for the new DSLs mentioned above, there are six new extensions:
- Azure Storage Data Lake (JVM only)
- Freemarker (native)
- HL7 (native)
- Huawei Cloud SMN (JVM only)
- Paho MQTT 5 (native)
- Stitch (JVM only)
These three extensions are now supported in native mode:
camel-quarkus-endpointdslare a part of
camel-quarkus-coresince long, so you can remove them safely making sure that your application depends on
camel-quarkus-coreeither directly or indirectly.
camel-quarkus-mainis now a part of
camel-quarkus-coreand you can remove it safely making sure that your projects depends on
camel-quarkus-coreat least transitively.
The following deprecated extensions were removed in this release:
- WebSocket JSR 356 (replaced by Vert.x WebSocket)
- All AWS SDK v1 extensions (replaced by their AWS SDK v2 counterparts)
A part of the functionality originally present in
camel-quarkus-xml-io has moved to
camel-quarkus-xml-io-dsl. Hence when you see e.g.
Cannot find RoutesBuilderLoader in classpath supporting file extension: xml in your log, you’ll need to replace
Full Changelog of Camel Quarkus 1.8.0
- Upgrading to Jackson 2.12.1 via Quarkus BOM 1.12 breaks Azure SDK v12 extensions - possible workaround: force Jackson 2.11.3 in your application
Quarkus team just announced their plans for 2.0 release integrating MicroProfile 4 and Vert.x 4. We will adapt to those changes and publish Camel Quarkus 2.0 alphas and betas following the respective Quarkus milestones. In the mean time, we may still consider releasing 1.9.0 if we have enough material for it.