|
| 1 | +--- |
| 2 | +title: "Apache Camel 4.14 What's New" |
| 3 | +date: 2025-08-20 |
| 4 | +draft: false |
| 5 | +authors: [ davsclaus,gzurowski,christophd] |
| 6 | +categories: [ "Releases" ] |
| 7 | +preview: "Details of what we have done in the Camel 4.14 LTS release." |
| 8 | +--- |
| 9 | + |
| 10 | +Apache Camel 4.14 LTS has just been [released](/blog/2025/08/RELEASE-4.14.0/). |
| 11 | + |
| 12 | +This release introduces a set of new features and noticeable improvements that we will cover in this blog post. |
| 13 | + |
| 14 | +## Camel Core |
| 15 | + |
| 16 | +Camel consumers will now eagerly setup MDC logging which makes it possible to include details such as `routeId` in logs while the consumer |
| 17 | +is being created and started up. |
| 18 | + |
| 19 | +The Intercept EIP now includes more details where the message was intercepted (node id and other information). |
| 20 | + |
| 21 | +## Camel Management |
| 22 | + |
| 23 | +We made it easier to control routes by their grouping, for example to stop a set of routes. |
| 24 | + |
| 25 | +Stopping routes will keep their JMX processor MBeans making troubleshooting easier, as you can investigate all the statistics of the processors. |
| 26 | + |
| 27 | +There are now _dump_ methods to dump statistics in JSon format as well. |
| 28 | + |
| 29 | +## Camel JBang |
| 30 | + |
| 31 | +Camel JBang now uses JDK21 as default instead of 17. |
| 32 | + |
| 33 | +We added support for controlling Camel routes by groups, so you can start and stop entire set of routes, using `camel cmd start-group` and `camel cmd stop-group`. |
| 34 | + |
| 35 | + |
| 36 | + |
| 37 | +You can now enable and disable EIPs dynamically using the `camel cmd enable-processor` and `camel cmd disable-processor`. |
| 38 | + |
| 39 | +`camel debug` has undergone many improvements and now runs slightly faster. |
| 40 | + |
| 41 | +`camel debug` now supports debugging Camel Spring Boot applications, by executing `camel debug pom.xml` which will |
| 42 | +detect that it's a Camel Spring Boot Maven project, and then startup Spring Boot via `mvn spring-boot:run` and attach |
| 43 | +the Camel route debugger automatically. |
| 44 | + |
| 45 | +`camel debug` can now step forward to a given _index_ which makes it fast to jump to a position such as if you restart |
| 46 | +the application and want to debug from a problematic spot during troubleshooting. |
| 47 | + |
| 48 | +The `camel kubernetes` plugin now better supports running and exporting a project by a directory name, and referring to a relative directory |
| 49 | +from where the command is being executed; making it more similar to `camel run` command. |
| 50 | + |
| 51 | +The `camel infra` command has been overhauled to better control and manage multiple processors. |
| 52 | + |
| 53 | +`camel test` is a new Camel JBang plugin that enables you to initialize and prototype some automated tests for the Camel routes. |
| 54 | +You need to add the plugin to your local Camel JBang tooling with `camel plugin add test`. |
| 55 | +Then you can use the plugin commands such as `camel test init` and `camel test run`. |
| 56 | + |
| 57 | +## Camel Groovy |
| 58 | + |
| 59 | +You can now preload shared Groovy sources such as DTOs and common functions, and make those available on the classpath, |
| 60 | +for entire Camel to use, such as from other components, dataformats, and Java. |
| 61 | + |
| 62 | +All you have to do is putting the groovy files in `src/main/resources/camel-groovy`, and add `camel-groovy` as dependency. |
| 63 | + |
| 64 | +This also works to hot update in Camel JBang dev mode, so you can edit the source, and automatically update Camel, making it |
| 65 | +very fast for coding in low-code style. |
| 66 | + |
| 67 | +## Camel Spring Boot |
| 68 | + |
| 69 | +`camel-spring-boot` is upgraded to the latest Spring Boot 3.5.4 release. |
| 70 | + |
| 71 | +## Java 25 |
| 72 | + |
| 73 | +We have prepared the code-base for the upcoming Java 25 release. However, this release does |
| 74 | +not officially support Java 25, but we are not aware of any issues (feedback is welcome). |
| 75 | +We will work on official Java 25 support in the following releases. |
| 76 | + |
| 77 | +## Miscellaneous |
| 78 | + |
| 79 | +Upgraded many third-party dependencies to the latest releases at the time of release. |
| 80 | + |
| 81 | +We made `camel-smb` more resilient and better recover when there are connectivity problems. |
| 82 | + |
| 83 | +`camel-rabbitmq` has improved performance in the producer. |
| 84 | + |
| 85 | +## New Components |
| 86 | + |
| 87 | +- `camel-iso8583` - Create, edit and read ISO-8583 messages |
| 88 | +- `came-langchain4j-agent` - AI Agent |
| 89 | + |
| 90 | +## Upgrading |
| 91 | + |
| 92 | +Make sure to read the [upgrade guide](/manual/camel-4x-upgrade-guide-4_14.html) if you are upgrading from a previous |
| 93 | +Camel version. |
| 94 | + |
| 95 | +If you are upgrading from, for example, 4.4 to 4.8, then make sure to follow the upgrade guides for each release |
| 96 | +in-between, i.e. |
| 97 | +4.4 -> 4.5, 4.5 -> 4.6, and so forth. |
| 98 | + |
| 99 | +The Camel Upgrade Recipes tool can also be used to automate upgrading. |
| 100 | +See more at: https://github.com/apache/camel-upgrade-recipes |
| 101 | + |
| 102 | +## Release Notes |
| 103 | + |
| 104 | +You can find additional information about this release in the list of resolved JIRA tickets: |
| 105 | + |
| 106 | +- [Release notes 4.14](/releases/release-4.14.0/) |
| 107 | + |
| 108 | +## Roadmap |
| 109 | + |
| 110 | +The following 4.15 release is planned for October 2025. |
| 111 | + |
0 commit comments