gansheer commented on code in PR #1292:
URL: https://github.com/apache/camel-website/pull/1292#discussion_r1950568925
##########
content/blog/2025/02/camel410-whatsnew/index.md:
##########
@@ -0,0 +1,244 @@
+---
+title: "Apache Camel 4.10 What's New"
+date: 2025-02-12
+authors: [davsclaus, orpiske, tadayosi]
+categories: ["Releases"]
+preview: Details of what we have done in the Camel 4.10 release.
+---
+
+Apache Camel 4.10 LTS has just been [released](/blog/2025/02/RELEASE-4.10.0/).
+
+This release introduces a set of new features and noticeable improvements that
we will cover in this blog post.
+
+## Camel Core
+
+Added `customize` to `RouteBuilder` to make it easier to configure a specific
Camel component / dataformat, service
+from a Java lambda style, such as follows:
+
+```java
+@Override
+public void configure() throws Exception {
+ customize(KServeComponent.class, k -> {
+ k.getConfiguration().setTarget("localhost:8888");
+ });
+
+ from("timer:kserve?repeatCount=1")
+ .to("kserve:model/metadata?modelName=myModel")
+ .log("${body}");
+}
+```
+
+This makes it possible for low-code users that want to have a single Java file
with the Camel route
+and all the Java based configuration done entirely from the same `configure`
method.
+
+## Camel JBang
+
+Using _modeline_ has been deprecated. It is recommended to configure
externally in the `application.properties`
+file, and then include this file when running with Camel JBang:
+
+```bash
+$ camel run foo.camel.yaml application.properties
+```
+
+Or use `*` to include all files from the current folder:
+
+```bash
+$ camel run *
+```
+
+We have continued to improve the `run` and `export` to work better and also
when using different runtimes.
+
+The `debug` command now supports step in and step over. For example debugging
a splitter allows
+now to step over and continue after the entire split is complete, while step
in, will step
+inside the splitter (default mode).
+
+The `shell` command has been improved, and can now be used for sub commands
such as `log` and `trace` or `--watch` mode,
+and be able to exit logging and still be within the shell. Previously you
would quit the shell when pressing `ctrl + c`.
+
+### Camel JBang Infra
+
+The new Camel JBang `infra` command provides access to external services used
for testing Apache Camel.
+This feature enables developers to quickly set up testing environments and
create prototypes using real services.
+
+The `infra` command offers two sub-commands:
+
+* `camel infra list`: Available external services
+* `camel infra run $SERVICE_ALIAS`: Run a service from the list
+
+For example, to start an FTP service, use:
+
+```bash
+$ camel infra run ftp
+
+Starting service ftp
+{
+ "getPort" : 52472,
+ "getFtpRootDir" :
"file://path/to/current/directory/target/ftp/camel-test-infra-test-directory/camel-test-infra-configuration-test-directory"
+}
+```
+
+The command returns a JSON response containing service configuration details
that can be directly integrated into your Camel routes.
+In this example, the response includes:
+
+* The dynamically assigned port number
+* The FTP root directory path
+
+This structured output makes it easy to programmatically access service
details in your development workflow.
+
+### Camel JBang Update
+
+The new Camel JBang `update` command streamlines the process of upgrading
Apache Camel applications to newer versions.
+The `update` command provides two sub-command:
+
+* `list`: Displays all available Apache Camel versions that you can upgrade to.
+* `run`: Performs the actual update process, automatically migrating your
application to the specified Camel version.
+
+The update process leverages the
https://github.com/apache/camel-upgrade-recipes[Apache Camel Open Rewrite
recipes] and supports three runtimes:
+
+* Plain Camel (camel-main)
+* Camel Quarkus (quarkus)
+* Camel Spring Boot (spring-boot)
+
+More information can be found in
https://camel.apache.org/manual/camel-jbang.html#_update[Apache Camel JBang
documentation].
+
+### Camel JBang Kubernetes
+
+TODO:
Review Comment:
```suggestion
We have done many improvements and bug fixes to make camel kubernetes work
well on Openshift and
[Minikube](https://camel.apache.org/manual/camel-jbang-kubernetes.html#_minikube_deployment_tips_and_troubleshooting).
The option `--name` has been added to allow the user to explicitly define
the integration name. It is available on all `camel kubernetes` commands.
The `--quiet` mode for camel kubernetes run command has been modified to
only show errors for build/deploy. Alternatively to display Maven build output
and JIB logs you can use `--verbose` mode.
```
@tdiesler I think you also did some work on registry.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
