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


The following commit(s) were added to refs/heads/main by this push:
     new 710004d9bb34 Regen
710004d9bb34 is described below

commit 710004d9bb346b4edd7e6f4d9e828f5ec7b19403
Author: Claus Ibsen <[email protected]>
AuthorDate: Mon Sep 14 10:29:03 2026 +0200

    Regen
---
 .../pages/camel-yaml-dsl-validator-maven-plugin.adoc     | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git 
a/docs/user-manual/modules/ROOT/pages/camel-yaml-dsl-validator-maven-plugin.adoc
 
b/docs/user-manual/modules/ROOT/pages/camel-yaml-dsl-validator-maven-plugin.adoc
index 6772173b4f8f..7ef2b1d3a00f 100644
--- 
a/docs/user-manual/modules/ROOT/pages/camel-yaml-dsl-validator-maven-plugin.adoc
+++ 
b/docs/user-manual/modules/ROOT/pages/camel-yaml-dsl-validator-maven-plugin.adoc
@@ -3,6 +3,7 @@
 The Camel YAML DSL Validator Maven Plugin supports the following goals
 
  - camel-yaml-dsl-validator:validate - To validate YAML routes are correct 
according to spec
+ - camel-yaml-dsl-validator:generate-doc-samples - Used by the Camel build to 
generate the YAML samples of the AI tools from the documentation
 
 == camel-yaml-dsl-validator:validate
 
@@ -152,3 +153,18 @@ You can pass in the options using `-D` style as shown:
 cd myproject
 mvn org.apache.camel:camel-yaml-dsl-validator:4.18.0:validate 
-Dcamel.includeTest=true
 ----
+
+== camel-yaml-dsl-validator:generate-doc-samples
+
+This goal is used by the Camel build itself, in `camel-jbang-core`, and is not 
intended for end users.
+
+It reads the `[source,yaml]` route examples of the EIP documentation and of 
the user manual, validates every one of
+them against the YAML DSL JSON Schema, and fails the build when an example 
does not validate. The examples that pass
+are written to `eip-samples.json`, keyed by the EIP or file entry they show 
(`split`, `onException`, `rest`, `beans`,
+...), which is what the `camel_catalog_sample` tool of the 
xref:manual::camel-jbang-mcp.adoc[Camel JBang MCP server]
+(and of the Camel TUI) returns as the fallback when the catalog in use has no 
documentation for the name.
+
+The pages are configured in the `pom.xml` of `camel-jbang-core`: the user 
manual pages whose examples are the samples
+of a file entry (`pages`), the pages whose examples starting with a given 
entry are its samples (`entryPages`), and the
+user manual pages that are not validated because they deliberately show old 
syntax (`excludes`, such as the upgrade
+guides). Every page of the EIP documentation is read, keyed by its file name.

Reply via email to