This is an automated email from the ASF dual-hosted git repository. luigidemasi pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel-kit.git
commit 2a9cf3fd25a64733ebd2484fc0a2ea4eeb51fd9c Author: Luigi De Masi <[email protected]> AuthorDate: Fri Oct 23 10:00:01 2026 +0200 docs: address the review of the Getting started pages Correct four statements that a reader could act on: - the migration page promised that init --here leaves the build files alone; init writes or replaces mvnw, mvnw.cmd and maven-wrapper.properties even without --force (InitService.createMavenWrapper), so the page now says so and asks to commit or back up a customized wrapper first; - the BizTalk example tested the transformed XML with a bean-style Simple expression; xslt-saxon returns a string, so the decision now uses XPath. The MuleSoft sub-flow and choice examples read JSON the same way; they now unmarshal the payload and use the map lookup syntax; - direct migration mode exists only in the development snapshot, not in release 0.4.1; the index and install pages now say that the documentation follows the development branch and mark such features, and the Codex Ship worker and the CLAUDE.md wording are adjusted the same way; - hdfs2 to hdfs is no longer offered as a Camel 4 rename: camel-hdfs was removed in Camel 4.4 and is absent from the 4.22.1 catalog. Rebuilt locally with the Camel website UI bundle: 27 pages, no warnings. --- docs/modules/ROOT/pages/agents.adoc | 6 +++--- docs/modules/ROOT/pages/getting-started.adoc | 7 ++++--- docs/modules/ROOT/pages/index.adoc | 5 +++-- docs/modules/ROOT/pages/migration-biztalk.adoc | 5 ++++- docs/modules/ROOT/pages/migration-camel-upgrade.adoc | 3 ++- docs/modules/ROOT/pages/migration-mulesoft.adoc | 11 +++++++++-- docs/modules/ROOT/pages/migration.adoc | 7 ++++++- 7 files changed, 31 insertions(+), 13 deletions(-) diff --git a/docs/modules/ROOT/pages/agents.adoc b/docs/modules/ROOT/pages/agents.adoc index fca1263d..565ac232 100644 --- a/docs/modules/ROOT/pages/agents.adoc +++ b/docs/modules/ROOT/pages/agents.adoc @@ -31,7 +31,7 @@ reports. [[claude]] == Anthropic Claude Code -`init` writes `CLAUDE.md` (which imports `AGENTS.md`), the slash commands under `.claude/commands/`, the skills under +`init` writes `CLAUDE.md` (which points to `AGENTS.md`), the slash commands under `.claude/commands/`, the skills under `.claude/skills/`, project settings in `.claude/settings.json` and the MCP servers in `.mcp.json`. Start with `/camel-start`. During `/camel-execute`, independent tasks of the same wave are dispatched to parallel subagents with isolated context windows. @@ -92,8 +92,8 @@ codex ---- `init` writes `AGENTS.md`, the skills under `.agents/skills/`, the custom agent roles under `.codex/agents/` -(planner, implementer, tester, validator, migrator, catalog researcher, security reviewer and a Ship worker) and the -three MCP servers in `.codex/config.toml`. It does not create `.codex/commands/`: Codex discovers the skills +(planner, implementer, tester, validator, migrator, catalog researcher and security reviewer; the development +snapshot adds a Ship worker) and the three MCP servers in `.codex/config.toml`. It does not create `.codex/commands/`: Codex discovers the skills directly, so you start with `$camel-start` after trusting the repository, and inspect skills with `/skills` and servers with `/mcp`. diff --git a/docs/modules/ROOT/pages/getting-started.adoc b/docs/modules/ROOT/pages/getting-started.adoc index bc6f150a..9759a480 100644 --- a/docs/modules/ROOT/pages/getting-started.adoc +++ b/docs/modules/ROOT/pages/getting-started.adoc @@ -39,8 +39,9 @@ warnings without stopping. == Release channels -This documentation describes Camel Kit {camel-kit-version}, which pairs with Knowledge MCP -{camel-kit-knowledge-version}. Pin the release when you need a reproducible installation. +This documentation follows the development branch ({camel-kit-snapshot-version}). The latest release is Camel Kit +{camel-kit-version}, which pairs with Knowledge MCP {camel-kit-knowledge-version}; features that are not in the +release are marked as development snapshot only. Pin the release when you need a reproducible installation. [cols="1,2,1"] |=== @@ -197,7 +198,7 @@ What every target gets:: * `.camel-kit/` with the project configuration, cached catalogs and templates, and later the pipeline state. * The MCP configuration for the target: JSON for most agents, `.codex/config.toml` for Codex, `.mcp.json` read through `pi-mcp-adapter` for Pi. -* `mvnw`, `mvnw.cmd` and `.mvn/wrapper/maven-wrapper.properties`. +* `mvnw`, `mvnw.cmd` and `.mvn/wrapper/maven-wrapper.properties`, written or replaced even when they exist. === Configuration diff --git a/docs/modules/ROOT/pages/index.adoc b/docs/modules/ROOT/pages/index.adoc index bddebd4f..37344c7c 100644 --- a/docs/modules/ROOT/pages/index.adoc +++ b/docs/modules/ROOT/pages/index.adoc @@ -6,8 +6,9 @@ testing, and runtime verification, and it checks every component and option agai does so. It is available as a standalone command-line tool and as a Camel JBang plugin, and it generates the same skills for several coding agents. -This documentation describes Camel Kit {camel-kit-version} with Knowledge MCP {camel-kit-knowledge-version}, -which target Camel {camel-version}. +This documentation follows the development branch of Camel Kit ({camel-kit-snapshot-version}). The latest release +is Camel Kit {camel-kit-version} with Knowledge MCP {camel-kit-knowledge-version}, which target Camel +{camel-version}; features that are not in the release are marked as development snapshot only. == What it does diff --git a/docs/modules/ROOT/pages/migration-biztalk.adoc b/docs/modules/ROOT/pages/migration-biztalk.adoc index 6aa80b04..3d3cee02 100644 --- a/docs/modules/ROOT/pages/migration-biztalk.adoc +++ b/docs/modules/ROOT/pages/migration-biztalk.adoc @@ -202,7 +202,7 @@ The `OrderToInvoiceMap` in this orchestration has at least 20 leaf fields and a uri: "xslt-saxon:kaoto-datamapper-a1b2c3d4.xsl" - choice: when: - - simple: "${body.amount} > 1000" + - xpath: "/Invoice/Amount > 1000" steps: - to: "direct:high-value-processing" otherwise: @@ -210,6 +210,9 @@ The `OrderToInvoiceMap` in this orchestration has at least 20 leaf fields and a - to: "direct:standard-processing" ---- +The `xslt-saxon` step returns the transformed document as a string, so the decision reads it with XPath; a +bean-style Simple expression on the body would fail. + [[manual-review]] == Flagged for manual review diff --git a/docs/modules/ROOT/pages/migration-camel-upgrade.adoc b/docs/modules/ROOT/pages/migration-camel-upgrade.adoc index 47aff4ed..86224fcc 100644 --- a/docs/modules/ROOT/pages/migration-camel-upgrade.adoc +++ b/docs/modules/ROOT/pages/migration-camel-upgrade.adoc @@ -56,12 +56,13 @@ Camel version and runtime, and a component that is not listed is checked there t | `http4`, `https4` | `http`, `https` | Renamed in 3.0 | `netty4`, `netty4-http` | `netty`, `netty-http` | -| `mina2`, `quartz2`, `mongodb3`, `hdfs2`, `rxjava2` | `mina`, `quartz`, `mongodb`, `hdfs`, `rxjava` | +| `mina2`, `quartz2`, `mongodb3`, `rxjava2` | `mina`, `quartz`, `mongodb`, `rxjava` | | `swagger-java` | `openapi-java` | | `ibatis`, `mqtt` | `mybatis`, `paho` | | `direct-vm`, `vm` | `direct`, `seda` | Cross-context variants removed in 4.0 | `aws-*` | `aws2-*` | AWS SDK v2; `aws-swf` was removed, use `aws2-step-functions` | `dozer` | Removed | Extract the mapping and use DataMapper +| `hdfs2`, `hdfs` | Removed | `camel-hdfs` was removed in Camel 4.4; choose a replacement and verify it in the catalog | `boon`, `jibx`, `linkedin`, `ironmq`, `etcd`, `ganglia`, `spark-rest`, `chronicle-engine`, `rx-netty` | Removed | The agent stops and asks; suggested alternatives include `jackson`, `jaxb`, `aws2-sqs`, `consul`, `micrometer` and `platform-http` diff --git a/docs/modules/ROOT/pages/migration-mulesoft.adoc b/docs/modules/ROOT/pages/migration-mulesoft.adoc index 7d41e0f2..67b772e6 100644 --- a/docs/modules/ROOT/pages/migration-mulesoft.adoc +++ b/docs/modules/ROOT/pages/migration-mulesoft.adoc @@ -193,6 +193,8 @@ both syntaxes. parameters: httpMethodRestrict: POST steps: + - unmarshal: + json: {} - to: "direct:validate-order" - route: id: validate-order @@ -200,11 +202,16 @@ both syntaxes. uri: "direct:validate-order" steps: - validate: - simple: "${body.orderId} != null" + simple: "${body[orderId]} != null" ---- +The JSON body is unmarshalled to a map before the sub-route reads it; a bean-style `body.orderId` expression on the +raw JSON string would fail. + === Choice router +Conditional routing on a JSON payload that an earlier step unmarshalled to a map. + .Mule XML [source,xml] ---- @@ -223,7 +230,7 @@ both syntaxes. ---- - choice: when: - - simple: ${body.amount} > 1000 + - simple: ${body[amount]} > 1000 steps: - to: direct:high-value-processing otherwise: diff --git a/docs/modules/ROOT/pages/migration.adoc b/docs/modules/ROOT/pages/migration.adoc index ad476465..2919578c 100644 --- a/docs/modules/ROOT/pages/migration.adoc +++ b/docs/modules/ROOT/pages/migration.adoc @@ -24,7 +24,9 @@ covers Fuse). [[init]] == Initialize the project for migration -Run `init` inside the existing project with `--here`; the existing source and build files are not modified. +Run `init` inside the existing project with `--here`. The application sources and `pom.xml` are left alone, but +`init` writes or replaces `mvnw`, `mvnw.cmd` and `.mvn/wrapper/maven-wrapper.properties` even without `--force`, +so commit or back up a customized Maven wrapper first. [source,bash] ---- @@ -66,6 +68,9 @@ scan, detection and analysis steps and then implements the route files and prope runs the adversarial review and starts the application with your explicit authorization. It writes a `MIGRATION.md` note instead of the four-document package and does not invoke `/camel-plan`. +NOTE: Direct mode is development snapshot only ({camel-kit-snapshot-version}); release {camel-kit-version} always +produces the design package. + [[discovery]] == Discovery
