[camel] 03/03: Upgrade guides about changes

[da...@apache.org]

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

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

commit b7a2fd9e201ef8b2e9dd131cffdba86ddf9d78ae
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Wed May 17 09:08:11 2023 +0200

    Upgrade guides about changes
---
 .../ROOT/pages/camel-3x-upgrade-guide-3_20.adoc    |  8 +++
 .../ROOT/pages/camel-3x-upgrade-guide-3_21.adoc    |  2 +
 .../ROOT/pages/camel-4-migration-guide.adoc        | 62 ++++++++++++----------
 3 files changed, 44 insertions(+), 28 deletions(-)

diff --git a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_20.adoc b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_20.adoc
index 32927e389c3..5932a7d8bad 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_20.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_20.adoc
@@ -4,6 +4,14 @@ This document is for helping you upgrade your Apache Camel application
 from Camel 3.x to 3.y. For example if you are upgrading Camel 3.0 to 3.2, then you should follow the guides
 from both 3.0 to 3.1 and 3.1 to 3.2.
 
+== Upgrading Camel 3.20.4 to 3.20.5
+
+In Camel JBang the `-dir` parameter for `init` and `run` goal has been renamed to require 2 dashes `--dir` like all the other options.
+
+== Upgrading Camel 3.20.3 to 3.20.4
+
+No changes
+
 == Upgrading Camel 3.20.2 to 3.20.3
 
 The option `backlogTracing=true` now automatic enabled the tracer on startup. The previous behavior
diff --git a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_21.adoc b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_21.adoc
index 276fd54e3d1..c9b0c06b1e9 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_21.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_21.adoc
@@ -69,6 +69,8 @@ XML parsers has been made more secure by disabling DOCTYPE and/or access to exte
 
 The command `camel dependencies` has been renamed to `camel dependency`.
 
+In Camel JBang the `-dir` parameter for `init` and `run` goal has been renamed to require 2 dashes `--dir` like all the other options.
+
 === camel-spring-boot
 
 The health-check has aligned to be more similar to microprofile-health in the JSon output.
diff --git a/docs/user-manual/modules/ROOT/pages/camel-4-migration-guide.adoc b/docs/user-manual/modules/ROOT/pages/camel-4-migration-guide.adoc
index 16a00c44c9f..515192c87fb 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4-migration-guide.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4-migration-guide.adoc
@@ -262,35 +262,13 @@ The metrics has been renamed to follow Micrometer naming convention https://micr
 | CamelRoutesRunning | camel.routes.running
 |===
 
-== Camel Spring Boot
-
-The `camel-spring-boot` dependency no longer includes `camel-spring-xml`. To use legacy Spring XML files `<beans>`
-with Camel on Spring Boot, then include the `camel-spring-boot-xml-starter` dependency.
-
-=== camel-micrometer-starter
-
-The `uri` tags are now static instead of dynamic (by default), as potential too many tags generated due to URI with dynamic values.
-This can be enabled again by setting `camel.metrics.uriTagDynamic=true`.
-
-=== camel-platform-http-starter
-
-The `platform-http-starter` has been changed from using `camel-servlet` to use Spring HTTP server directly.
-Therefore, all the HTTP endpoints are no longer prefixed with the servlet context-path (default is `camel`).
+== camel-jbang
 
-For example:
-
-[source,java]
-----
-from("platform-http:myservice")
-  .to("...")
-----
+The command `camel dependencies` has been renamed to `camel dependency`.
 
-Then calling _myservice_ would before require to include the context-path, such as `http://localhost:8080/camel/myservice`.
-Now the context-path is not in use, and the endpoint can be called with `http://localhost:8080/myservice`.
-
-NOTE: The `platform-http-starter` can also be used with Rest DSL.
+In Camel JBang the `-dir` parameter for `init` and `run` goal has been renamed to require 2 dashes `--dir` like all the other options.
 
-== camel-openapi-java
+=== camel-openapi-java
 
 The `camel-openapi-java` component has been changed to use `io.swagger.v3` libraries instead of `io.apicurio.datamodels`.
 As a result, the return type of the public method org.apache.camel.openapi.RestOpenApiReader.read() is now `io.swagger.v3.oas.models.OpenAPI` instead of `io.apicurio.datamodels.openapi.models.OasDocument`.
@@ -298,8 +276,7 @@ When an OpenAPI 2.0 (swagger) specification is parsed, it is automatically upgra
 This version also supports OpenAPI 3.1.x specifications.
 The related spring-boot starter components have been modified to use the new return type.
 
-
-== camel-optaplanner
+=== camel-optaplanner
 
 The `camel-optaplanner` component has been change to use `SolverManager`. If you were using `SoverManager` in Camel 3, you don't need anymore the boolean useSolverManager in the Route.
 Deprecated `ProblemFactChange` has been replaced by `ProblemChange`.
@@ -329,3 +306,32 @@ from("optaplanner:myProblemName?configFile=PATH/TO/CONFIG.FILE.xml")
 
 Solver Daemon solutions should be migrated to use SolverManager.
 
+
+== Camel Spring Boot
+
+The `camel-spring-boot` dependency no longer includes `camel-spring-xml`. To use legacy Spring XML files `<beans>`
+with Camel on Spring Boot, then include the `camel-spring-boot-xml-starter` dependency.
+
+=== camel-micrometer-starter
+
+The `uri` tags are now static instead of dynamic (by default), as potential too many tags generated due to URI with dynamic values.
+This can be enabled again by setting `camel.metrics.uriTagDynamic=true`.
+
+=== camel-platform-http-starter
+
+The `platform-http-starter` has been changed from using `camel-servlet` to use Spring HTTP server directly.
+Therefore, all the HTTP endpoints are no longer prefixed with the servlet context-path (default is `camel`).
+
+For example:
+
+[source,java]
+----
+from("platform-http:myservice")
+  .to("...")
+----
+
+Then calling _myservice_ would before require to include the context-path, such as `http://localhost:8080/camel/myservice`.
+Now the context-path is not in use, and the endpoint can be called with `http://localhost:8080/myservice`.
+
+NOTE: The `platform-http-starter` can also be used with Rest DSL.
+