You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Andrea Cosentino (Jira)" <ji...@apache.org> on 2020/06/11 10:00:00 UTC

[jira] [Assigned] (CAMEL-15169) camel-hdfs: does not work (on Camel Kafka Connector) due to dependencies conflicts

     [ https://issues.apache.org/jira/browse/CAMEL-15169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrea Cosentino reassigned CAMEL-15169:
----------------------------------------

    Assignee: Andrea Cosentino

> camel-hdfs: does not work (on Camel Kafka Connector) due to dependencies conflicts
> ----------------------------------------------------------------------------------
>
>                 Key: CAMEL-15169
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15169
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-hdfs
>    Affects Versions: 3.3.0
>            Reporter: Otavio Rodolfo Piske
>            Assignee: Andrea Cosentino
>            Priority: Major
>
> This is a problem that was originally referenced on the [Camel Kafka Connector issue #263 on Github|https://github.com/apache/camel-kafka-connector/issues/263] and describes a problem trying to load the HDFS connector on the Kafka Connect runtime. 
>  ---
> It seems that the HDFS Connector cannot be loaded due to conflicts between the dependencies used by the component and the ones available on the connect runtime.
> Without manipulating the classpath, loading the dependencies fail because a dependency carried by either one of them does not seem to contain the getProperties on the Application class (which comes from {{javax.ws.rs:javax.ws.rs-api}}). Manipulating the classpath to include this library and/or exclude specific dependencies cause the connector to fail to load due to other classpath related issues (ie.: {{ClassNotFoundException}}).
> ---
> According to the discussion on the ticket, it may be more suitable to perform the fix on the Camel HDFS component. Therefore, raising this issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)