essobedo commented on code in PR #1071: URL: https://github.com/apache/camel-website/pull/1071#discussion_r1348454398
########## content/blog/2023/10/migrate4/index.md: ########## @@ -0,0 +1,44 @@ +--- +title: "Migrating to Apache Camel 4" +date: 2023-10-10 +authors: [davsclaus] +categories: ["Howtos"] +preview: Guidelines for migrating to Apache Camel 4 +--- + +Apache Camel 4 was released a few months back. This blog post is a general guideline for Camel users +that are seeking information how to migrate from Camel 2 or 3. + +We plan to post more blog posts in the future with more specific details on migrating, such as migrating from Camel Karaf +to Camel 4 on Spring Boot or Quarkus. + +Apache Camel 4.0 is a fork of Camel 3.20. In other words, after the 3.20.0 release, we shifted the `main` +code branch to be Camel 4. This affects how to migrate to Camel 4, as you essentially need to migrate to Camel 3.20 first. +And then afterward you can migrate to Camel 4.x. + +Camel 4 requirements: + +- Java 17 or 21 (Official Java 21 support is planned for Camel 4.2) +- Spring Boot 3 +- Quarkus 3 +- Jakarta EE APIs + +Migration Plan: + +1. Migrate from Camel 2.x to 3.0 (only relevant for Camel 2 users) +2. Upgrade from Camel 3.x to 3.20 +3. Migrate from Camel 3.20 to 4.0 +4. Upgrade from 4.0.x to 4.x + +You can find more details in the [migration and upgrade guides](/manual/migration-and-upgrade.html). + +We anticipate the migration effort for most end users from Camel 3 to 4 is a _minor effort_, as Camel 4 +was a release lead by Spring Boot 3, Quarkus 3, and `javax` -> `jakarta` API. Review Comment: ```suggestion was a release led by Spring Boot 3, Quarkus 3, and Jakarta EE migration. ``` -- 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: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
