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-kamelets.git
The following commit(s) were added to refs/heads/main by this push:
new 07b06f989 chore: rebrand Camel JBang to Camel CLI and use relative
link in docs
07b06f989 is described below
commit 07b06f989e48a3ab35a86fd2b803db59d1571f49
Author: Claus Ibsen <[email protected]>
AuthorDate: Sat Jul 4 21:52:09 2026 +0200
chore: rebrand Camel JBang to Camel CLI and use relative link in docs
Co-Authored-By: Claude Opus 4.6 <[email protected]>
---
docs/modules/ROOT/pages/development.adoc | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/docs/modules/ROOT/pages/development.adoc
b/docs/modules/ROOT/pages/development.adoc
index ecfe22129..f80c18976 100644
--- a/docs/modules/ROOT/pages/development.adoc
+++ b/docs/modules/ROOT/pages/development.adoc
@@ -35,7 +35,7 @@ We're going to show an example shortly.
Suppose that you want to provide a Kamelet that allows users to search data on
Twitter, providing a stream of information about a given keyword.
Creating such a Kamelet is a fairly easy task: we can use options of the
"camel-twitter" component without adding much processing logic.
-So the procedure of writing a simple Kamelet starts with scaffolding a new
Kamelet resource, which can be done with the Camel JBang CLI (`camel`):
+So the procedure of writing a simple Kamelet starts with scaffolding a new
Kamelet resource, which can be done with the Camel CLI (`camel`):
[source]
----
@@ -487,7 +487,7 @@ We write it using the Java DSL because that is the language
that most Apache Cam
TIP: For a great developer experience, we suggest to use
https://code.visualstudio.com/[Visual Studio Code] with the
https://marketplace.visualstudio.com/items?itemName=redhat.apache-camel-extension-pack[Camel
Extension Pack]
-We start from scratch by creating an integration file with Camel JBang CLI:
+We start from scratch by creating an integration file with Camel CLI:
[source]
----
@@ -530,7 +530,7 @@ simpler solution that just requires your own machine:
camel run Earthquake.java
----
-The `camel run` command relies on Camel JBang to locally run the integration.
The integration will start and begin printing out earthquake data every 10
seconds.
+The `camel run` command relies on Camel CLI to locally run the integration.
The integration will start and begin printing out earthquake data every 10
seconds.
I show an excerpt of what is printed by the integration:
@@ -1424,7 +1424,7 @@ The most obvious way to test a Kamelet is via an e2e
tests that verifies if the
https://github.com/citrusframework/citrus[Citrus] is the framework of choice
for such e2e tests. Integration tests live
under `tests/camel-kamelets-itest/src/test/resources/<feature>/`: each one is
a Citrus `+*.citrus.it.yaml+` test that
-drives the Kamelet with https://camel.apache.org/manual/camel-jbang.html[Camel
JBang] -- it runs a Camel `Pipe` that
+drives the Kamelet with xref:manual::camel-jbang.adoc[Camel CLI] -- it runs a
Camel `Pipe` that
wires the Kamelet under test and then asserts the resulting behaviour.
The building blocks of a test are:
@@ -1476,7 +1476,7 @@ variables:
- name: "message"
value: "Hello from the log-sink test!"
actions:
- # Run the Pipe as a Camel JBang integration
+ # Run the Pipe as a Camel CLI integration
- camel:
jbang:
run:
