You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "davsclaus (via GitHub)" <gi...@apache.org> on 2023/10/06 07:47:25 UTC
[PR] Camel 4 general migrate blog [camel-website]
davsclaus opened a new pull request, #1071:
URL: https://github.com/apache/camel-website/pull/1071
WIP.
Feedback and review is welcome.
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Camel 4 general migrate blog [camel-website]
Posted by "essobedo (via GitHub)" <gi...@apache.org>.
essobedo commented on code in PR #1071:
URL: https://github.com/apache/camel-website/pull/1071#discussion_r1348411519
##########
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 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.
+
+There are Camel components that has been removed in Camel 4 as they were either deprecated in v3, or they do
Review Comment:
```suggestion
There are Camel components that have been removed in Camel 4 as they were either deprecated in v3, or they do
```
##########
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 based on the Camel 3.20.0 release. In other words, after the 3.20.0 release, we shifted the `main`
Review Comment:
```suggestion
Apache Camel 4.0 is a fork of Camel 3.20. In other words, after the 3.20.0 release, we shifted the `main`
```
##########
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 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.
Review Comment:
Jakarta EE migration instead of "`javax` -> `jakarta` API"
##########
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 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.
+
+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).
+
+In terms of backward compatibility, then Camel 4 is mostly compatible with regular Camel applications.
+However, if you are using some of the more advanced features and other plugins in Camel, then migrating
Review Comment:
```suggestion
However, if you are using some advanced features and other plugins in Camel, then migrating
```
Not sure what you mean by "other plugins in Camel"
##########
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
Review Comment:
```suggestion
We plan to post more blog posts in the future with specific details on migrating, such as migrating from Camel Karaf
```
##########
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 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.
+
+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
Review Comment:
```suggestion
not support Jakarta EE, or their underlying project is no longer active. You can find a list of components
```
##########
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 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.
+
+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).
Review Comment:
```suggestion
that have been removed (with suggestions for new components to use) in the [camel 4 migration guide](manual/camel-4-migration-guide.html).
```
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Camel 4 general migrate blog [camel-website]
Posted by "davsclaus (via GitHub)" <gi...@apache.org>.
davsclaus commented on PR #1071:
URL: https://github.com/apache/camel-website/pull/1071#issuecomment-1750501649
There is some feedback on the user mailing list - such as for advanced use with Camel then you need to use PluginHelper and also its a bit different how to get hold of `ExtendedCamelContext`
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Camel 4 general migrate blog [camel-website]
Posted by "davsclaus (via GitHub)" <gi...@apache.org>.
davsclaus commented on PR #1071:
URL: https://github.com/apache/camel-website/pull/1071#issuecomment-1750209317
Thanks @essobedo you are welcome to do the updates if you want, and add as author ;)
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Camel 4 general migrate blog [camel-website]
Posted by "essobedo (via GitHub)" <gi...@apache.org>.
essobedo commented on PR #1071:
URL: https://github.com/apache/camel-website/pull/1071#issuecomment-1750287302
> Thanks @essobedo you are welcome to do the updates if you want, and add as author ;)
I'm done, thx
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Camel 4 general migrate blog [camel-website]
Posted by "essobedo (via GitHub)" <gi...@apache.org>.
essobedo commented on code in PR #1071:
URL: https://github.com/apache/camel-website/pull/1071#discussion_r1348459852
##########
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 launch a series of blog posts in the near 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 led by Spring Boot 3, Quarkus 3, and Jakarta EE migration.
Review Comment:
```suggestion
was a release led by Spring Boot 3, Quarkus 3, and the 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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Camel 4 general migrate blog [camel-website]
Posted by "davsclaus (via GitHub)" <gi...@apache.org>.
davsclaus merged PR #1071:
URL: https://github.com/apache/camel-website/pull/1071
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Camel 4 general migrate blog [camel-website]
Posted by "essobedo (via GitHub)" <gi...@apache.org>.
essobedo commented on code in PR #1071:
URL: https://github.com/apache/camel-website/pull/1071#discussion_r1348458077
##########
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
Review Comment:
```suggestion
We plan to launch a series of blog posts in the near future with more specific details on migrating, such as migrating from Camel Karaf
```
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Camel 4 general migrate blog [camel-website]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #1071:
URL: https://github.com/apache/camel-website/pull/1071#issuecomment-1754957238
🚀 Preview is available at https://pr-1071--camel.netlify.app
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Camel 4 general migrate blog [camel-website]
Posted by "essobedo (via GitHub)" <gi...@apache.org>.
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org