Apache Camel 3.14 has just been released. This is the last LTS release supporting Java 8, and therefore we have extended the support period from 1 to 2 years. This blog post first details the noteworthy changes since the last 3.11 LTS release from 6 months ago. So what’s in this release (6 months of work) This release introduces a set of new features and noticeable improvements that we will cover in this blog post.
I’m an engineer working at the OSS solution center of Hitachi, Ltd. Hitachi, Ltd. is a company that provides IT services & platforms in Japan and other countries. In our organization, OSS solution center, we are working on providing the IT services with the OSS. In my case, I’m working on Keycloak, 3scale and Camel, providing the technical support and considering the use cases of them. And I’m also an open source contributor for Keycloak.
Apache Camel is NOT using log4j for production Apache Camel does not directly depend on Log4j 2, so we are not affected by CVE-2021-44228. If you explicitly added the Log4j 2 dependency to your own applications, make sure to upgrade. Apache Camel is using log4j for testing itself Apache Camel does use log4j during testing itself, and therefore you can find that we have been using log4j v2.13.3 release in our latest LTS releases Camel 3.