luigidemasi opened a new issue, #51: URL: https://github.com/apache/camel-kit/issues/51
> Imported from [luigidemasi/camel-kit#90](https://github.com/luigidemasi/camel-kit/issues/90), opened by [cunningt](https://github.com/cunningt) on 2026-05-28. --- Tried /camel-migrate (used claude) of a camel-spring-boot 3 project to get it to camel-spring-boot 4 - it did a lot of really smart things that I don't think the camel-upgrade-recipes are capable of yet - it knew to turn camel-swagger-java-starter to camel-openapi-starter, but there were a few things I found that I think could be improved and that might help migrations from other vendors as well - **versions** : I have a `<camel-spring-boot-version/>` that is used for com.redhat.camel.springboot.platform:camel-spring-boot-bom. The migration saw that I was using a redhat version and chose a redhat version to upgrade to, but it chose `<camel-spring-boot-version>4.14.4.redhat-00008</camel-spring-boot-version> ` That's a version that exists for camel, but that version does not exist for camel-spring-boot. For the camel-spring-boot bom or for -starter dependencies that are part of camel-spring-boot, we should be using camel-spring-boot versions (like 4.14.2.redhat-00010) It'd be pretty cool if it could match the correct camel version for the camel-spring-boot version (or vice versa) as well. - the migration chose spring-boot 3.2.5 - it should choose the version that was specified in org.apache.camel.springboot:spring-boot (for 4.14.2.redhat-00010 it was 3.5.11) or that was specified in camel-parent (for camel versions 4.15.0+) - I'm a little unsure of what it did around activemq for migration - should camel-kit include knowledge of other RH projects that historically have been linked to camel (like activemq, apicurio, etc) [mymigration.tar.gz](https://github.com/user-attachments/files/28369412/mymigration.tar.gz) [original.tar.gz](https://github.com/user-attachments/files/28369425/original.tar.gz) -- 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]
