[camel-website] branch m4 created (now b3b2cda2)

[da...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a change to branch m4
in repository https://gitbox.apache.org/repos/asf/camel-website.git


      at b3b2cda2 Camel 4 general migrate blog

This branch includes the following new commits:

     new b3b2cda2 Camel 4 general migrate blog

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.

[camel-website] 01/01: Camel 4 general migrate blog

[da...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch m4
in repository https://gitbox.apache.org/repos/asf/camel-website.git

commit b3b2cda21ac6df54715f93f307681e2e19cfeaa1
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Fri Oct 6 09:46:50 2023 +0200

    Camel 4 general migrate blog
---
 content/blog/2023/10/migrate4/featured.png | Bin 0 -> 243818 bytes
 content/blog/2023/10/migrate4/index.md     |  41 +++++++++++++++++++++++++++++
 2 files changed, 41 insertions(+)

diff --git a/content/blog/2023/10/migrate4/featured.png b/content/blog/2023/10/migrate4/featured.png
new file mode 100644
index 00000000..a9a95d3b
Binary files /dev/null and b/content/blog/2023/10/migrate4/featured.png differ
diff --git a/content/blog/2023/10/migrate4/index.md b/content/blog/2023/10/migrate4/index.md
new file mode 100644
index 00000000..6a5d3b38
--- /dev/null
+++ b/content/blog/2023/10/migrate4/index.md
@@ -0,0 +1,41 @@
+---
+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 based on the Camel 3.20.0 release. 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. 
+
+However, there are Camel components that has been removed in Camel 4 as they were either deprecated in v3, or they do
+not support Jakarta EE, or their project is no longer active. You can find a list of components
+that has been removed (with suggestion for new component to use) in the [camel 4 migration guide](manual/camel-4-migration-guide.html).
+