Every javax import in every route
Camel 3 is past community end of life. Camel 4 moved to the Jakarta EE namespaces and raised the Java baseline to 17 -- and drags Spring Boot 2 to 3 along with it.
Challenge
Camel 4 is a coordinated change across every route, custom processor, type converter and test in the estate, with a full integration regression behind it. Camel Spring Boot pins a compatible Spring Boot line, so the Jakarta migration arrives twice.
Environment
Apache Camel 3.x with a large route estate, typically on Spring Boot 2.x, past community end of life.
Approach
OSSeva patches the Camel 3 line so the integration estate is not running unpatched while the Jakarta migration is planned, and scopes the Camel 4 move against the actual route inventory.
What this delivers
A patched integration layer, and a Camel 4 migration sized against the real route count rather than started under a CVE deadline.