Removed docs and regen
diff --git a/docs/modules/ROOT/pages/connectors.adoc b/docs/modules/ROOT/pages/connectors.adoc
index 09e6b25..c06f902 100644
--- a/docs/modules/ROOT/pages/connectors.adoc
+++ b/docs/modules/ROOT/pages/connectors.adoc
@@ -2,7 +2,7 @@
= Supported connectors and documentation
// kafka-connectors list: START
-Number of Camel Kafka connectors: 334
+Number of Camel Kafka connectors: 332
[width="100%",cols="4,1,1,1,1,1,1",options="header"]
|===
@@ -62,12 +62,10 @@
| *camel-beanstalk-kafka-connector* | true | true | xref:connectors/camel-beanstalk-kafka-sink-connector.adoc[Sink Docs] | xref:connectors/camel-beanstalk-kafka-source-connector.adoc[Source Docs] | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-beanstalk-kafka-connector/0.5.0/camel-beanstalk-kafka-connector-0.5.0-package.zip[Download Zip] | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-beanstalk-kafka-connector/0.5.0/camel-beanstalk-kafka-connector-0.5.0-package.tar.gz[Download Tar.gz]
| *camel-box-kafka-connector* | true | true | xref:connectors/camel-box-kafka-sink-connector.adoc[Sink Docs] | xref:connectors/camel-box-kafka-source-connector.adoc[Source Docs] | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-box-kafka-connector/0.5.0/camel-box-kafka-connector-0.5.0-package.zip[Download Zip] | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-box-kafka-connector/0.5.0/camel-box-kafka-connector-0.5.0-package.tar.gz[Download Tar.gz]
| *camel-braintree-kafka-connector* | true | true | xref:connectors/camel-braintree-kafka-sink-connector.adoc[Sink Docs] | xref:connectors/camel-braintree-kafka-source-connector.adoc[Source Docs] | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-braintree-kafka-connector/0.5.0/camel-braintree-kafka-connector-0.5.0-package.zip[Download Zip] | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-braintree-kafka-connector/0.5.0/camel-braintree-kafka-connector-0.5.0-package.tar.gz[Download Tar.gz]
-| *camel-browse-kafka-connector* | true | true | xref:connectors/camel-browse-kafka-sink-connector.adoc[Sink Docs] | xref:connectors/camel-browse-kafka-source-connector.adoc[Source Docs] | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-browse-kafka-connector/0.5.0/camel-browse-kafka-connector-0.5.0-package.zip[Download Zip] | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-browse-kafka-connector/0.5.0/camel-browse-kafka-connector-0.5.0-package.tar.gz[Download Tar.gz]
| *camel-caffeine-cache-kafka-connector* | true | false | xref:connectors/camel-caffeine-cache-kafka-sink-connector.adoc[Sink Docs] | | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-caffeine-cache-kafka-connector/0.5.0/camel-caffeine-cache-kafka-connector-0.5.0-package.zip[Download Zip] | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-caffeine-cache-kafka-connector/0.5.0/camel-caffeine-cache-kafka-connector-0.5.0-package.tar.gz[Download Tar.gz]
| *camel-caffeine-loadcache-kafka-connector* | true | false | xref:connectors/camel-caffeine-loadcache-kafka-sink-connector.adoc[Sink Docs] | | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-caffeine-loadcache-kafka-connector/0.5.0/camel-caffeine-loadcache-kafka-connector-0.5.0-package.zip[Download Zip] | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-caffeine-loadcache-kafka-connector/0.5.0/camel-caffeine-loadcache-kafka-connector-0.5.0-package.tar.gz[Download Tar.gz]
| *camel-chatscript-kafka-connector* | true | false | xref:connectors/camel-chatscript-kafka-sink-connector.adoc[Sink Docs] | | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-chatscript-kafka-connector/0.5.0/camel-chatscript-kafka-connector-0.5.0-package.zip[Download Zip] | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-chatscript-kafka-connector/0.5.0/camel-chatscript-kafka-connector-0.5.0-package.tar.gz[Download Tar.gz]
| *camel-chunk-kafka-connector* | true | false | xref:connectors/camel-chunk-kafka-sink-connector.adoc[Sink Docs] | | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-chunk-kafka-connector/0.5.0/camel-chunk-kafka-connector-0.5.0-package.zip[Download Zip] | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-chunk-kafka-connector/0.5.0/camel-chunk-kafka-connector-0.5.0-package.tar.gz[Download Tar.gz]
-| *camel-class-kafka-connector* | true | false | xref:connectors/camel-class-kafka-sink-connector.adoc[Sink Docs] | | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-class-kafka-connector/0.5.0/camel-class-kafka-connector-0.5.0-package.zip[Download Zip] | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-class-kafka-connector/0.5.0/camel-class-kafka-connector-0.5.0-package.tar.gz[Download Tar.gz]
| *camel-cm-sms-kafka-connector* | true | false | xref:connectors/camel-cm-sms-kafka-sink-connector.adoc[Sink Docs] | | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-cm-sms-kafka-connector/0.5.0/camel-cm-sms-kafka-connector-0.5.0-package.zip[Download Zip] | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-cm-sms-kafka-connector/0.5.0/camel-cm-sms-kafka-connector-0.5.0-package.tar.gz[Download Tar.gz]
| *camel-cmis-kafka-connector* | true | true | xref:connectors/camel-cmis-kafka-sink-connector.adoc[Sink Docs] | xref:connectors/camel-cmis-kafka-source-connector.adoc[Source Docs] | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-cmis-kafka-connector/0.5.0/camel-cmis-kafka-connector-0.5.0-package.zip[Download Zip] | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-cmis-kafka-connector/0.5.0/camel-cmis-kafka-connector-0.5.0-package.tar.gz[Download Tar.gz]
| *camel-coap-kafka-connector* | true | true | xref:connectors/camel-coap-kafka-sink-connector.adoc[Sink Docs] | xref:connectors/camel-coap-kafka-source-connector.adoc[Source Docs] | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-coap-kafka-connector/0.5.0/camel-coap-kafka-connector-0.5.0-package.zip[Download Zip] | https://repo.maven.apache.org/maven2/org/apache/camel/kafkaconnector/camel-coap-kafka-connector/0.5.0/camel-coap-kafka-connector-0.5.0-package.tar.gz[Download Tar.gz]
diff --git a/docs/modules/ROOT/pages/connectors/camel-browse-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-browse-kafka-sink-connector.adoc
deleted file mode 100644
index 8adb0b7..0000000
--- a/docs/modules/ROOT/pages/connectors/camel-browse-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,55 +0,0 @@
-// kafka-connector options: START
-[[camel-browse-kafka-connector-sink]]
-= camel-browse-kafka-connector sink configuration
-
-When using camel-browse-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-browse-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.browse.CamelBrowseSinkConnector
-----
-
-
-The camel-browse sink connector supports 6 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Priority
-| *camel.sink.path.name* | A name which can be any string to uniquely identify the endpoint | null | HIGH
-| *camel.sink.endpoint.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | MEDIUM
-| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM
-| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | MEDIUM
-| *camel.component.browse.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | MEDIUM
-| *camel.component.browse.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM
-|===
-
-
-
-The camel-browse sink connector has no converters out of the box.
-
-
-
-
-
-The camel-browse sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-browse sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-browse-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-browse-kafka-source-connector.adoc
deleted file mode 100644
index 9c62392..0000000
--- a/docs/modules/ROOT/pages/connectors/camel-browse-kafka-source-connector.adoc
+++ /dev/null
@@ -1,57 +0,0 @@
-// kafka-connector options: START
-[[camel-browse-kafka-connector-source]]
-= camel-browse-kafka-connector source configuration
-
-When using camel-browse-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-browse-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Source connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.browse.CamelBrowseSourceConnector
-----
-
-
-The camel-browse source connector supports 8 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Priority
-| *camel.source.path.name* | A name which can be any string to uniquely identify the endpoint | null | HIGH
-| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | MEDIUM
-| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | MEDIUM
-| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | MEDIUM
-| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM
-| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | MEDIUM
-| *camel.component.browse.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | MEDIUM
-| *camel.component.browse.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM
-|===
-
-
-
-The camel-browse sink connector has no converters out of the box.
-
-
-
-
-
-The camel-browse sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-browse sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-class-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-class-kafka-sink-connector.adoc
deleted file mode 100644
index 3e594a1..0000000
--- a/docs/modules/ROOT/pages/connectors/camel-class-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,61 +0,0 @@
-// kafka-connector options: START
-[[camel-class-kafka-connector-sink]]
-= camel-class-kafka-connector sink configuration
-
-When using camel-class-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.kafkaconnector</groupId>
- <artifactId>camel-class-kafka-connector</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel Kafka connector version -->
-</dependency>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.clazz.CamelClassSinkConnector
-----
-
-
-The camel-class sink connector supports 12 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Priority
-| *camel.sink.path.beanName* | Sets the name of the bean to invoke | null | HIGH
-| *camel.sink.endpoint.cache* | Use scope option instead. | null | LOW
-| *camel.sink.endpoint.method* | Sets the name of the method to invoke on the bean | null | MEDIUM
-| *camel.sink.endpoint.scope* | Scope of bean. When using singleton scope (default) the bean is created or looked up only once and reused for the lifetime of the endpoint. The bean should be thread-safe in case concurrent threads is calling the bean at the same time. When using request scope the bean is created or looked up once per request (exchange). This can be used if you want to store state on a bean while processing a request and you want to call the same bean instance multiple times while processing the request. The bean does not have to be thread-safe as the instance is only called from the same request. When using prototype scope, then the bean will be looked up or created per call. However in case of lookup then this is delegated to the bean registry such as Spring or CDI (if in use), which depends on their configuration can act as either singleton or prototype scope. so when using prototype then this depends on the delegated registry. One of: [Singleton] [Request] [Prototype] | "Singleton" | MEDIUM
-| *camel.sink.endpoint.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | MEDIUM
-| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM
-| *camel.sink.endpoint.parameters* | Used for configuring additional properties on the bean | null | MEDIUM
-| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | MEDIUM
-| *camel.component.class.cache* | Use singleton option instead. | "true" | LOW
-| *camel.component.class.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | MEDIUM
-| *camel.component.class.scope* | Scope of bean. When using singleton scope (default) the bean is created or looked up only once and reused for the lifetime of the endpoint. The bean should be thread-safe in case concurrent threads is calling the bean at the same time. When using request scope the bean is created or looked up once per request (exchange). This can be used if you want to store state on a bean while processing a request and you want to call the same bean instance multiple times while processing the request. The bean does not have to be thread-safe as the instance is only called from the same request. When using delegate scope, then the bean will be looked up or created per call. However in case of lookup then this is delegated to the bean registry such as Spring or CDI (if in use), which depends on their configuration can act as either singleton or prototype scope. so when using prototype then this depends on the delegated registry. One of: [Singleton] [Request] [Prototype] | "Singleton" | MEDIUM
-| *camel.component.class.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM
-|===
-
-
-
-The camel-class sink connector has no converters out of the box.
-
-
-
-
-
-The camel-class sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-class sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END
