Blog post featured image

Image by Anders Lanzen CC BY-NC-SA 2.0

We are pleased to announce the release 2.0.0 of Camel Quarkus. It brings Quarkus 2.0, Camel 3.11, improved test coverage and 13 new or promoted extensions. Many thanks to all contributors and issue reporters!

Quarkus 2.0.0.Final

Like in Camel 3.11, in Quarkus 2.0, Vert.x and MicroProfile were upgraded to their newest major versions 4. Further, in Quarkus 2.0, Java 8 support was dropped permanently and Java 11 is the minimal supported version. 21.1 is the recommended version of GraalVM.

When it comes to developer experience, Quarkus 2.0 introduces continuous testing. Quarkus dev mode (a.k.a. mvn quarkus:dev) exists since the very beginnings of Quarkus. It not only starts your application so that you can test it manually, but it also keeps watching for changes in your workspace, recompiling the modified classes as needed and reloading the running application. Now with continuous testing, your tests are executed as you change your application code. You have to press r to enable it. You may want to watch this video to learn more about the new continuous testing feature.

Please refer to Quarkus 2.0.0.Final announcement for more details.

Camel 3.11.0

Please check the What’s new in Camel 3.11.0 blog post for more information.

New extensions and promotions to native

New extensions:

Extensions newly supported in native mode:

Test coverage and closing functionality gaps

In this release, we invested a lot of effort into reviewing existing tests and adding new test cases. We proceeded methodically, following the main Camel documentation. We took care to cover every use case mentioned on the Camel component pages. For example for the HTTP component, we went through the use cases mentioned on its component page , and we checked whether they are covered by existing tests. All the missing scenarios were listed in a “Test expansion” issue and fixed by adding the respective tests .

In this way, we not only found and fixed bugs, but we also uncovered fully missing features. This was the case e.g. with @org.apache.camel.EndpointInject, @org.apache.camel.Produce and @org.apache.camel.Consume annotations from camel-core. These are supported by Camel Quarkus now - see here and here .

The extent of this effort can be assessed by running this GitHub issues query . This endeavour is going to continue in coming Camel Quarkus releases.

Deprecations

  • Avro extension: @BuildTimeAvroDataFormat is deprecated - see the Avro extension page.

Breaking changes and migration steps

Please refer to our 2.0.0 Migration guide .

Release notes

Fixed issues:

All commits: