[camel] branch main updated: camel-threadpoolfactory-vertx is experimental

[da...@apache.org]

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 f79d1f166db camel-threadpoolfactory-vertx is experimental
f79d1f166db is described below

commit f79d1f166dbff521e9e3d98a84cd648c9f284dd9
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Sun Apr 2 14:35:40 2023 +0200

    camel-threadpoolfactory-vertx is experimental
---
 components/camel-threadpoolfactory-vertx/pom.xml           |  2 +-
 .../src/generated/resources/threadpoolfactory-vertx.json   |  2 +-
 .../src/main/docs/threadpoolfactory-vertx.adoc             | 14 +++++++-------
 3 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/components/camel-threadpoolfactory-vertx/pom.xml b/components/camel-threadpoolfactory-vertx/pom.xml
index fb3b4ddbcae..dee9c677c84 100644
--- a/components/camel-threadpoolfactory-vertx/pom.xml
+++ b/components/camel-threadpoolfactory-vertx/pom.xml
@@ -35,7 +35,7 @@
         <firstVersion>3.5.0</firstVersion>
         <label>reactive</label>
         <title>ThreadPoolFactory Vert.x</title>
-        <supportLevel>preview</supportLevel>
+        <supportLevel>experimental</supportLevel>
     </properties>
 
     <dependencies>
diff --git a/components/camel-threadpoolfactory-vertx/src/generated/resources/threadpoolfactory-vertx.json b/components/camel-threadpoolfactory-vertx/src/generated/resources/threadpoolfactory-vertx.json
index 3e25c2a36fe..a565d6427c0 100644
--- a/components/camel-threadpoolfactory-vertx/src/generated/resources/threadpoolfactory-vertx.json
+++ b/components/camel-threadpoolfactory-vertx/src/generated/resources/threadpoolfactory-vertx.json
@@ -7,7 +7,7 @@
     "deprecated": false,
     "firstVersion": "3.5.0",
     "label": "reactive",
-    "supportLevel": "Preview",
+    "supportLevel": "Experimental",
     "groupId": "org.apache.camel",
     "artifactId": "camel-threadpoolfactory-vertx",
     "version": "4.0.0-SNAPSHOT"
diff --git a/components/camel-threadpoolfactory-vertx/src/main/docs/threadpoolfactory-vertx.adoc b/components/camel-threadpoolfactory-vertx/src/main/docs/threadpoolfactory-vertx.adoc
index 91f9f1bf2a6..6233bb7e9be 100644
--- a/components/camel-threadpoolfactory-vertx/src/main/docs/threadpoolfactory-vertx.adoc
+++ b/components/camel-threadpoolfactory-vertx/src/main/docs/threadpoolfactory-vertx.adoc
@@ -4,20 +4,20 @@
 :artifactid: camel-threadpoolfactory-vertx
 :description: ThreadPoolFactory for camel-core using Vert.x
 :since: 3.5
-:supportlevel: Preview
+:supportlevel: Experimental
 
 *Since Camel {since}*
 
 The camel-threadpoolfactory-vertx is a VertX based implementation of the `ThreadPoolFactory` SPI.
 
-By default Camel will use its own thread pool for EIPs that can use parallel processing (such as splitter, aggregator).
-You can plugin different engines via a SPI interface. This is a VertX based plugin that uses the VertX worker thread pool
+By default, Camel will use its own thread pool for EIPs that can use parallel processing (such as splitter, aggregator).
+You can plug in different engines via an SPI interface. This is a VertX based plugin that uses the VertX worker thread pool
 (executeBlocking).
 
 == Restrictions
 
 This implementation has been designed to use VertX worker threads for EIPs where concurrency has been enabled (using default settings).
-However this is limited to only apply when the EIP are not configured with a specific thread pool. For example the first example
+However, this is limited to only apply when the EIP are not configured with a specific thread pool. For example the first example
 below will use VertX worker threads, and the 2nd below will not:
 
 [source,java]
@@ -50,10 +50,10 @@ from("direct:start")
 
 == VertX instance
 
-This implementation will first lookup in the registry for an existing `io.vertx.core.Vertx` to be used.
-However you can configure an existing instance using the getter/setter on the `VertXThreadPoolFactory` class.
+This implementation will first look up in the registry for an existing `io.vertx.core.Vertx` to be used.
+However, you can configure an existing instance using the getter/setter on the `VertXThreadPoolFactory` class.
 
-== Auto detection from classpath
+== Auto-detection from classpath
 
 To use this implementation all you need to do is to add the `camel-threadpoolfactory-vertx` dependency to the classpath,
 and Camel should auto-detect this on startup and log as follows: