This is an automated email from the ASF dual-hosted git repository. christophd pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel.git
commit c91fed0060f3b7b287ae7c9f9fbb44d8bfc67240 Author: Christoph Deppisch <[email protected]> AuthorDate: Thu Oct 15 08:35:33 2026 +0200 CAMEL-25378: Escape Citrus variable placeholder in adoc to fix website build Co-Authored-By: Claude Opus 4.6 <[email protected]> --- .../resources/org/apache/camel/catalog/docs/citrus-component.adoc | 2 +- .../camel-test/camel-test-citrus/src/main/docs/citrus-component.adoc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/citrus-component.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/citrus-component.adoc index 2d914f66c330..4400a11cfa3b 100644 --- a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/citrus-component.adoc +++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/citrus-component.adoc @@ -381,7 +381,7 @@ citrus.expectedMessageCount(1); === Exchange properties and variables as Citrus variables All exchange properties and exchange variables are automatically propagated to the Citrus test -context as test variables. This enables the use of Citrus variable placeholders (`${variableName}`) +context as test variables. This enables the use of Citrus variable placeholders (pass:c[`${variableName}`]) in expected message templates and response bodies. Variables extracted by Citrus during validation (e.g., via `@variable('name')@`) are written back diff --git a/components/camel-test/camel-test-citrus/src/main/docs/citrus-component.adoc b/components/camel-test/camel-test-citrus/src/main/docs/citrus-component.adoc index 2d914f66c330..4400a11cfa3b 100644 --- a/components/camel-test/camel-test-citrus/src/main/docs/citrus-component.adoc +++ b/components/camel-test/camel-test-citrus/src/main/docs/citrus-component.adoc @@ -381,7 +381,7 @@ citrus.expectedMessageCount(1); === Exchange properties and variables as Citrus variables All exchange properties and exchange variables are automatically propagated to the Citrus test -context as test variables. This enables the use of Citrus variable placeholders (`${variableName}`) +context as test variables. This enables the use of Citrus variable placeholders (pass:c[`${variableName}`]) in expected message templates and response bodies. Variables extracted by Citrus during validation (e.g., via `@variable('name')@`) are written back
