You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by da...@apache.org on 2019/12/18 19:12:09 UTC

[camel] 01/02: CAMEL-13903: Remove cxf import in pom

This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git

commit 89c0642606d406629076246deeaa49b4da9862a4
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Wed Dec 18 20:11:33 2019 +0100

    CAMEL-13903: Remove cxf import in pom
---
 components/camel-telegram/pom.xml                               | 6 ------
 components/camel-telegram/src/main/docs/telegram-component.adoc | 2 +-
 2 files changed, 1 insertion(+), 7 deletions(-)

diff --git a/components/camel-telegram/pom.xml b/components/camel-telegram/pom.xml
index 73a03b9..8dddc87 100644
--- a/components/camel-telegram/pom.xml
+++ b/components/camel-telegram/pom.xml
@@ -32,12 +32,6 @@
     <name>Camel :: Telegram</name>
     <description>Camel Telegram support</description>
 
-    <properties>
-        <camel.osgi.import.additional>
-            org.apache.cxf.*;version="${cxf-version-range}"
-        </camel.osgi.import.additional>
-    </properties>
-
     <dependencies>
         <dependency>
             <groupId>org.apache.camel</groupId>
diff --git a/components/camel-telegram/src/main/docs/telegram-component.adoc b/components/camel-telegram/src/main/docs/telegram-component.adoc
index b855e31..1f93c08 100644
--- a/components/camel-telegram/src/main/docs/telegram-component.adoc
+++ b/components/camel-telegram/src/main/docs/telegram-component.adoc
@@ -58,7 +58,7 @@ The Telegram component supports 7 options, which are listed below.
 | *authorizationToken* (security) | The default Telegram authorization token to be used when the information is not provided in the endpoints. |  | String
 | *client* (advanced) | To use a custom AsyncHttpClient |  | AsyncHttpClient
 | *clientConfig* (advanced) | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. |  | AsyncHttpClientConfig
-| *baseUri* (common) | Set an alternative base URI, e.g. when you want to test the component against a mock Telegram API. |  | String
+| *baseUri* (advanced) | Set an alternative base URI, e.g. when you want to test the component against a mock Telegram API. | https://api.telegram.org | String
 | *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
 | *lazyStartProducer* (producer) | 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 [...]
 | *bridgeErrorHandler* (consumer) | 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 | boolean