Re: Why is camel-kafka-starter excluding (transitive) dependency to Kafka artifacts (i.e. kafka-clients)?

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Re: Why is camel-kafka-starter excluding (transitive) dependency to Kafka artifacts (i.e. kafka-clients)?

Claus Ibsen-2

Oh it may be that spring boot comes with a set of -starter OOTB and
camel prefer to use those. I assume there is a spring-boot-kafka
dependency you can add which brings in the supported Kafka version for

On Mon, Sep 23, 2019 at 1:11 PM Erik Boye <[hidden email]> wrote:

> Hi,
> I am trying to figure out why camel-kafka-starter is excluding the transitive dependency to kafka-clients:
> The whole idea with Spring Boot Starters is "a one-stop-shop for all the Spring and related technology that you need without having to hunt through sample code and copy paste loads of dependency descriptors" (from In order to use camel-kafka, you obviously need a dependency to one or more Kafka artifacts, and I think those dependencies should be pulled in with camel-kafka-starter. So why the exclusion?
> This means that a cannot only depend on camel-kafka-starter to "get started", but I also have to explicitly add the dependency to kafka-clients. And maybe also kafka_2.11? I don't know, and I think that these exclusions ruin the starter concept for camel-kafka.....
> The versions of Kafka artifacts will be managed by Spring Boot BOM, but some artifact must declare the dependencies, and I think it should be camel-kafka-starter in this case.
> Is there any rationale behind that I do not understand?
> Regards,
> Erik
> "This email with attachments is solely for the use of the individual or entity to which it is addressed. It may contain confidential or privileged information. If you are not the addressee, please notify the sender and delete this message and all attachments from your files."

Claus Ibsen
----------------- @davsclaus
Camel in Action 2: