This is an automated email from the ASF dual-hosted git repository.
orpiske pushed a commit to branch orpiske-patch-1
in repository https://gitbox.apache.org/repos/asf/camel-website.git
commit 0935bd47dff3d6fdd9ff5841c6585d25f259b343
Author: Otavio Rodolfo Piske <orpi...@users.noreply.github.com>
AuthorDate: Mon Aug 14 13:48:31 2023 +0200
Apply editing changes for grammar check tools
---
content/blog/2023/08/camel4-whatsnew/index.md | 101 +++++++++++++-------------
1 file changed, 51 insertions(+), 50 deletions(-)
diff --git a/content/blog/2023/08/camel4-whatsnew/index.md
b/content/blog/2023/08/camel4-whatsnew/index.md
index 0c770c53..fbb87749 100644
--- a/content/blog/2023/08/camel4-whatsnew/index.md
+++ b/content/blog/2023/08/camel4-whatsnew/index.md
@@ -5,18 +5,17 @@ authors: [davsclaus,gzurowski,opiske]
categories: ["Releases"]
preview: Top 10 of what's new in Apache Camel version 4
---
-
-After 10 months of development, with 3 milestone, and 2 RC releases, then
Apache Camel v4 is released
-today as LTS release. The Camel `4.0.x` is a LTS release that is supported for
1 year.
+After 10 months of development, with 3 milestones, and 2 RC releases, we are
releasing Apache Camel v4
+today as LTS release. The Camel `4.0.x` is a LTS release, and we will support
it for 1 year.
This blog post highlights some noteworthy new features and improvements in
Camel v4.
-The features are based on work since January 2023, which was the time, where
we switched `main` branch
-to be Camel v4 based, and our effort was focused primary on Camel v4.
+The features are based on work since January 2023, which was the time when we
switched `main` branch to
+be Camel v4 based. Since then, we focused our effort primarily on Camel v4.
### 1) Major Goals
-The need for Camel 4 is mainly driven by Java open source projects migrating
from `javax` to `jakarta` APIs
+The need for Camel 4 is mainly driven by Java open source projects migrating
from `javax` to `jakarta` APIs,
and to keep up with popular runtimes such as Spring Boot and Quarkus.
1. Migrate from `javax` -> `jakarta` (JEE 10)
@@ -24,7 +23,7 @@ and to keep up with popular runtimes such as Spring Boot and
Quarkus.
3. Spring Boot 3
4. Quarkus 3
-Camel 4 requires Java 17. Support for Java 21 is planned for next LTS released
by end of this year.
+Camel 4 requires Java 17. We plan to support Java 21 on next LTS released by
the end of this year.
### 2) Dependency updates
@@ -38,7 +37,7 @@ You can find more details in this blog post [camel 4
performance improvements](/
### 4) Camel Spring Boot
-Camel 4 is at the time of release, tested with the latest Spring Boot 3.1.2
release.
+We tested Camel 4 with Spring Boot 3.1.2, the latest release available.
This release also comes with our first basic (and very limited) support for
Spring Boot native (AOT compilation).
See more in the
[aot-basic](https://github.com/apache/camel-spring-boot-examples/tree/main/aot-basic)
example.
@@ -53,48 +52,46 @@ Stay tuned for their release announcements.
For users that just want to run standalone Camel, then we have `camel-main`
that are constantly being improved.
The foundation in `camel-main` is reused by Camel Spring Boot, Camel Quarkus,
and Camel JBang as well.
-For Camel 4 we have made it possible to easily include an embedded HTTP server
with the new `camel-platform-http-main` module.
+The inclusion of an embedded HTTP server is now made easy with the new
`camel-platform-http-main` module.
See more in the
[camel-main](https://github.com/apache/camel-examples/tree/main/examples/main)
example.
### 7) Camel JBang
-A lot of improvements was put into `camel-jbang`. The `camel` CLI is now able
to easily run with different Camel versions,
-for example
+We made a lot of improvements to Camel JBang. The `camel` CLI can now easily
run with different Camel versions, for example:
camel run foo.yaml --camel-version=3.21.0
camel run foo.yaml --camel-version=3.20.6
-This is very handy when you for example need to trouble-shoot why _something_
started failed. It works on X but not on Y,
-and now you can quickly try and find out which version in between that started
failing.
+This is very handy when, for example, you need to trouble-shoot why
_something_ started failed. For instance, in occasions when
+it works on version X but not on version Y, now you can quickly try to find
out which version in between that started failing.
-You can also specify that `camel` CLI should by default use a specific Camel
version, for example if you have a newer version
-of Camel JBang installed but must develop and use an older release.
+You can also specify that `camel` CLI should use a specific Camel version by
default. For example, if you have a newer version of
+Camel JBang installed, but must develop and use an older release:
camel version set 3.20.6
-The following new commands has been added
+We added the following new commands:
-- `camel config` - to set custom user configuration
-- `camel log` - to show logs of your running Camel integrations (can show logs
for 1 or more Camel apps)
-- `camel trace` - to show message tracing of your running Camel integrations
(can show logs for 1 or more Camel apps)
-- `camel cmd send` - to send messages to an existing running Camel integration
-- `camel get route-dump` - to dump routes in XML or YAML format
+- `camel config`: you can use to set custom user configuration
+- `camel log`: you can use to show logs of your running Camel integrations
(can show logs for 1 or more Camel apps)
+- `camel trace`: you can use to show message tracing of your running Camel
integrations (can show logs for 1 or more Camel apps)
+- `camel cmd send`: you can use to send messages to an existing running Camel
integration
+- `camel get route-dump`: you can use to dump routes in XML or YAML format
-The maven resolver that Camel JBang uses has been migrated to latest, and
Camel JBang will now report more accurately
-whether a dependency was downloaded or resolved from a local maven repository.
The `camel run` command also has a `--verbose`
-flag to output more details in dependency resolution that can help during
troubleshooting.
+We migrated the maven resolver that Camel JBang uses to the latest version,
and Camel JBang will now report more accurately whether
+a dependency was downloaded or resolved from a local maven repository. The
`camel run` command also has a `--verbose` flag to output
+more details in dependency resolution that can help during troubleshooting.
The `camel-main` runtime now supports exporting with Kubernetes manifest and
build support, to make it easier to build
container images that are ready to run on Kubernetes.
-In general there has been many improvements to Camel JBang making this a great
way to try Camel, and as well as
-a companion tool you can use during traditional Camel development.
+We made many improvements to Camel JBang, making it a great way to experiment
with Camel and a useful companion tool for traditional
+Camel development.
### 8) XML DSL with beans
-We have been working on to unify the YAML, XML and Java DSL to be more aligned
in feature parity related
-to configuring beans. For example in XML DSL (`camel-xml-io`) you can now
declare beans and Camel routes in
-the same XML file with `<camel>` as the root tag:
+We have been working on to unify the YAML, XML and Java DSL, so that they have
feature parity related to configuring beans. For example,
+in XML DSL (`camel-xml-io`) you can now declare beans and Camel routes in the
same XML file with `<camel>` as the root tag:
```xml
<camel>
@@ -119,8 +116,8 @@ Then Camel handles the dependency injection, among the
`<beans>`.
You can also use Spring dependency injection (which is more advanced), by
inlining Spring `<beans>` tag with the spring namespace.
See more in the documentation for `camel-xml-io-dsl` module.
-There is more work to be done, and we are planning to see if we can also use
this to make migration from legacy
-OSGi Blueprint (and Spring XML files, eg `<beans>`) to modern Camel DSL.
+There is more work to be done, and we are planning to see if we can also use
this to simplify migrating from legacy OSGi Blueprint
+(and Spring XML files, eg `<beans>`) to the modern Camel DSL.
### 9) New components
@@ -136,15 +133,15 @@ OSGi Blueprint (and Spring XML files, eg `<beans>`) to
modern Camel DSL.
Camel 4 now requires JUnit 5 for unit tests, with the test components that
have -junit5 as suffix.
-If you work with XML or JSon payloads then the body can be logged in pretty
format with:
+If you work with XML or JSON payloads, then you can log the body in pretty
format with:
.log("${prettyBody}")
-And in XML
+And in XML:
<log message="${prettyBody}"/>
-And in YAML
+And in YAML:
- log: "${prettyBody}"
@@ -153,20 +150,26 @@ TODO: Other bits and pieces
### 11) Migrating to Camel 4
-We have of course cleaned up the code base, such as removing all deprecated
APIs and components.
-We have also adjusted some APIs in regard to configuring `CamelContext` with
custom settings.
+We have, of course, cleaned up the code base. For instance, we removed all the
deprecated APIs and components.
+
+We have also adjusted some APIs used to configure the `CamelContext` with
custom settings.
+
+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 the code
+to the new version might be needed.
-In terms of backward compatibility then Camel 4 is mostly compatible for
regular Camel applications.
-However, if you are using some of the more advanced features and other plugins
in Camel then migration is needed.
-Also, custom components must be migrated and recompiled.
-All details can be seen in the [migration
guide](/manual/camel-4-migration-guide.html).
+Additionally, custom components must be migrated and recompiled.
+
+You can learn about all details can in the [migration
guide](/manual/camel-4-migration-guide.html).
Good luck with your migration if you decide to continue your Camel journey.
And for new users to Camel then good luck getting onboard.
### 12) Roadmap for remainder of 2023
We will continue working on Camel 4.x and do non-LTS releases, leading up to
the next LTS release by end of this year.
-The major goals for this is Java 21 support, Spring Boot 3.2, and to catch up
with newer Quarkus releases.
+
+The major goals for this year are to support Java 21, Spring Boot 3.2, and to
catch up with newer Quarkus releases.
The following releases are currently scheduled (subject for change) for this
year:
@@ -174,17 +177,15 @@ The following releases are currently scheduled (subject
for change) for this yea
|---------|------|-------------|
| 4.1 | Oct | Non-LTS |
| 4.2 | Dec | LTS |
-
An ongoing effort is also to keep stabilizing our CI builds, to ensure commits
do not introduce regressions.
-At this moment then the CI builds are occasionally have a few test errors that
are related to flaky tests, that
-we keep fixing, to ensure the CI reports are trustworthy.
+At this moment, the CI builds are occasionally have a few test errors that are
related to flaky tests, that we keep fixing to
+ensure the CI reports are trustworthy.
-During the development of Camel 4, our community received many contributions
for improving Camel build and tests on higher
-end server platforms such as Power (ppc64le) and s390x (Linux On Mainframe).
Users and organizations building and leveraging
-Apache Camel on those platforms should have a smoother experience with Camel
4. This continues as an ongoing effort and
-we expect and even better experience for those platforms in subsequent
releases.
+Many people helped improve the Camel build and tests for high-end servers like
Power and s390x during Camel 4's development. Users
+and organizations building and leveraging Apache Camel on those platforms
should have a smoother experience with Camel 4. This
+continues as an ongoing effort and we expect and even better experience for
those platforms in subsequent releases.
-We will continue to look for areas where we can improve the performance of
Camel. At this point, we have identified that we
-can improve performance in the Camel type converter systems, and we plan to
refactor for Camel 4.1 onwards.
+We will continue to look for areas where we can improve the performance of
Camel. At this point, we have identified that we can
+improve performance in the Camel type converter systems, and we plan to
refactor for Camel 4.1 onwards.
And of course all the usual new features and improvements coming in from
community users and contributors.
