You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Jiri Ondrusek (Jira)" <ji...@apache.org> on 2024/06/19 09:17:00 UTC

[jira] [Created] (CAMEL-20896) Camel migrations

Jiri Ondrusek created CAMEL-20896:
-------------------------------------

             Summary: Camel migrations
                 Key: CAMEL-20896
                 URL: https://issues.apache.org/jira/browse/CAMEL-20896
             Project: Camel
          Issue Type: New Feature
    Affects Versions: 4.7.0
            Reporter: Jiri Ondrusek
            Assignee: Jiri Ondrusek


Quarkus introduced a migration tool in the past (see the documentation - [https://quarkus.io/guides/update-quarkus]). Camel Quarkus leveraged the tool 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:
 # The recipes should be moved into the Camel repository (together with the tests)
 # There should be an easy way of running those recipes on plain Camel projects
 # 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)
 # The Quarkus repository has to be refactored to use the Camel recipes (and tests) artifact



--
This message was sent by Atlassian Jira
(v8.20.10#820010)