Description
Hello Team,
We are upgrading Apache Camel from 3.x.x to 4.x.x using the migrate-camel-3-to-4 OpenRewrite recipe.
After running the following command:
mvn rewrite:run
The build completes successfully, but no code modifications are applied, and the Camel version is not updated in the pom.xml.
Observed Behavior
mvn rewrite:run finishes with BUILD SUCCESS
No Camel‑related code changes are performed
No version update in pom.xml
No refactoring logs indicating recipe execution
Environment / Recipes Applied
Before running the Camel upgrade recipe, we already applied:
UpgradeBuildToJava21
UpgradeSpringBoot_3_2
Our project currently builds and runs successfully after these upgrades.
Issue
The migrate-camel-3-to-4 recipe appears to run but does not apply any refactoring, even though:
We have multiple modules using Apache Camel
Several classes contain Camel imports
Camel dependencies exist in parent and child modules
Request
Could you please clarify whether:
Additional configuration is required?
The recipe requires specific dependency coordinates?
We need to activate a different recipe name/group?
This is a known issue or missing functionality in the recipe?
Any guidance would be greatly appreciated.
Description
Hello Team,
We are upgrading Apache Camel from 3.x.x to 4.x.x using the migrate-camel-3-to-4 OpenRewrite recipe.
After running the following command:
mvn rewrite:run
The build completes successfully, but no code modifications are applied, and the Camel version is not updated in the pom.xml.
Observed Behavior
mvn rewrite:run finishes with BUILD SUCCESS
No Camel‑related code changes are performed
No version update in pom.xml
No refactoring logs indicating recipe execution
Environment / Recipes Applied
Before running the Camel upgrade recipe, we already applied:
UpgradeBuildToJava21
UpgradeSpringBoot_3_2
Our project currently builds and runs successfully after these upgrades.
Issue
The migrate-camel-3-to-4 recipe appears to run but does not apply any refactoring, even though:
We have multiple modules using Apache Camel
Several classes contain Camel imports
Camel dependencies exist in parent and child modules
Request
Could you please clarify whether:
Additional configuration is required?
The recipe requires specific dependency coordinates?
We need to activate a different recipe name/group?
This is a known issue or missing functionality in the recipe?
Any guidance would be greatly appreciated.