The Integration is the resource which represents the actual Camel application and building a container image that packages the integration within an elevated cloud platform (be it locally in a Minikube or K8s hosted cluster to Openshift clusters) takes ample amount of time. Enhancing the Camel-K Integration build time Our goal was to reduce overhead and improve user experience. We were able to narrow down the major contributors that had a significant influence on the integration build time.
At the end of 2019 Camel 3 arrived. Some main features were modularization of the core and support for Java 11. A bunch of other changes were mentioned in Claus Ibsen’s blog: Apache Camel 3 What’s New (top 10) In this blog, we focus on the top 10 of features that arrived since the 3.0 release. As an overview, but also to give some attention to features not everyone is aware of.
, by Claus Ibsen, Gregor Zurowski, Nicolas Filotto, Otavio Rodolfo Piske, Alexandre Gallice, Aurélien Pupier, Zheng Feng
Apache Camel 3.17 has just been released. This release introduces a set of new features and noticeable improvements that we will cover in this blog post. Java 17 (runtime) support Camel 3.17 is the first release where we have official support for Java 17, really easy to remember :) That said, the Java 17 support is runtime only, meaning that we do not add special support for new Java 17 language features such as Java records.