Hi Jiri Thanks for bringing this to the community.
I think it would be a good idea to have migration rules/tools for Camel community users that they can assist with their upgrades. Especially if its neutral and can do this for the camel-core project that is essentially 99% of the upgrade for CSB or CEQ users too. On Thu, May 30, 2024 at 2:02 PM Jiří Ondrušek <ondrusek.j...@gmail.com> wrote: > Hi all, > > Quarkus introduced a migration tool in the past (see the documentation - > https://quarkus.io/guides/update-quarkus). We leveraged the tool in Camel > Quarkus and added support for migration of the camel-quarkus projects. Now > is the right time to bring such migrations into plain Camel. > > Current status: > • Quarkus migration tool uses OpenRewrite recipes > • Camel Quarkus added recipes for the migration of plain Camel from 3.x to > 4.x > • Recipes are located in the Quarkus repository ( > > https://github.com/quarkusio/quarkus-updates/tree/main/recipes/src/main/java/io/quarkus/updates/camel > ) > > I'd like to propose several improvements: > > 1. The recipes should be moved into the Camel repository (together with > the tests) > 2. There should be an easy way of running those recipes on plain Camel > projects > 3. The recipes module has to become a part of the released Camel bits > (it could be added as the last released module as nothing should depend > on > it) > 4. The Quarkus repository has to be refactored to use the Camel recipes > (and tests) artifact > > If there is an agreement on this task, I'd create a ticket for the work and > I'd like to take care of it. > > Best regards, > Jiri > -- Claus Ibsen ----------------- @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
