Croway opened a new issue, #131: URL: https://github.com/apache/camel-upgrade-recipes/issues/131
## Summary Track adding the OpenRewrite recipes for the Camel 4.22 → 4.23 migration, for both plain Camel (`camel-upgrade-recipes`) and Camel Spring Boot (`camel-spring-boot-upgrade-recipes`), following the [4.23 upgrade guide](https://camel.apache.org/manual/camel-4x-upgrade-guide-4_23.html). ## Planned coverage - ✅ csimple language / `camel-csimple-joor` / `camel-csimple-maven-plugin` removed → `simple` (Java API, XML DSL, YAML DSL) - ✅ `camel-zeebe` renamed to `camel-camunda` (dependency, `zeebe:`→`camunda:` URIs incl. `jobKey`→`jobType`, header names, model/constant types) - ✅ `camel-langchain4j-tools` module removed (dependency removal ordered so it doesn't defeat the 4.22 URI-migration precondition in the full migration chain) - ✅ `camel-ibm-cos` `CamelIBMCOSContentControl` → `CamelIBMCOSCacheControl` header rename - ✅ `camel-headersmap`, `camel-reactive-executor-vertx`, `camel-threadpoolfactory-vertx` removed - ✅ Spring Boot starter equivalents for the above (`camel-csimple-joor-starter`, `camel-langchain4j-tools-starter` → `camel-ai-tool-starter`, `camel-zeebe-starter` → `camel-camunda-starter`) - ❌/⚠️ Everything else in the guide with no safe mechanical rewrite is documented as not automated in `release_notes.adoc`, with the reason ## Known blocker Camel 4.23.0 (and the new `camel-camunda`, `camel-camunda-starter`, `camel-ai-tool-starter` artifacts) are not yet published to Maven Central. A handful of test assertions that depend on resolving those artifacts (a Maven-parser warning comment, or the `UpgradeDependencyVersion` catch-all silently declining to bump to an unresolvable version) will only go green once the release ships; this affects the whole existing test suite the moment `camel-latest-version` is bumped, not just the new 4.23 recipes. --- _Claude Code on behalf of croway_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
