Rebrand Camel JBang to Camel CLI

.asf.yaml

@@ -20,9 +20,19 @@ github:
   homepage: https://camel.apache.org
   labels:
     - camel
+    - examples
+    - spring-boot
     - integration
+    - integration-framework
+    - enterprise-integration-patterns
     - java
-    - spring-boot
+    - cloud-native
+    - kafka
+    - rest-api
+    - yaml
+    - data-transformation
+    - microservices
+    - mcp
   enabled_merge_buttons:
     merge: false
     rebase: true

ai-agent/README.adoc

@@ -25,8 +25,8 @@ This separation enables:
 
 === Prerequisites
 
-==== Camel JBang
-Install Camel JBang to easily run infrastructure services:
+==== Camel CLI
+Install Camel CLI to easily run infrastructure services:
 
     $ curl -Ls https://sh.jbang.dev | bash -s - trust add https://github.com/apache/camel/
     $ curl -Ls https://sh.jbang.dev | bash -s - app install --fresh --force camel@apache/camel
@@ -48,7 +48,7 @@ Make sure Ollama is running on `http://localhost:11434` (default port) or update
 NOTE: While you can use `camel infra run ollama` to run Ollama via Docker, be aware of performance limitations. On macOS, the Docker image cannot utilize GPU acceleration, making it extremely slow. Additionally, when running the Camel Ollama test-infra, both the Ollama Docker image and the default model (granite4, ~3GB) need to be downloaded on first run, which can be very time-consuming. For better performance, it's recommended to install Ollama natively.
 
 ==== Qdrant
-Use Camel JBang to run Qdrant:
+Use Camel CLI to run Qdrant:
 
     $ camel infra run qdrant
 

milvus/readme.adoc

@@ -15,7 +15,7 @@ The pipeline works end-to-end:
 
 === Prerequisites
 
-1. A running Milvus instance (using https://camel.apache.org/manual/camel-jbang.html[Camel JBang]):
+1. A running Milvus instance (using https://camel.apache.org/manual/camel-jbang.html[Camel CLI]):
 
 ----
 camel infra run milvus