[jira] [Resolved] (CAMEL-15273) Can I avoid the starters?

["Claus Ibsen (Jira)" <ji...@apache.org>]

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

Claus Ibsen resolved CAMEL-15273.
---------------------------------
    Resolution: Invalid

Use the mailing list for asking questions.

The starters are for spring boot and are best to be used, they have auto configuration and some have special spring boot integration.

But you can for most of them not use the starter if you dont use auto configuration.

And for maven you can use maven exclude to remove dependencies.

> Can I avoid the starters?
> -------------------------
>
>                 Key: CAMEL-15273
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15273
>             Project: Camel
>          Issue Type: Wish
>          Components: camel-spring-boot-starters
>    Affects Versions: 3.4.0
>            Reporter: Corneliu C
>            Priority: Minor
>         Attachments: Camel-starters.png
>
>
> Hi,
> I have a hard-time understanding how and why to use the new 3.4.x starters vs individual components, but this is what the documentation suggests.
> I have a hard time because they bring unnecessary JAR's which I have now to manage in pom.xml via exclusions.
> For example:
> {code:java}
> <!-- Camel -->
>  <dependency>
>  <groupId>org.apache.camel</groupId>
>  <artifactId>camel-support</artifactId>
>  </dependency>
>  <dependency>
>  <groupId>org.apache.camel.springboot</groupId>
>  <artifactId>camel-jsonpath-starter</artifactId>
>  </dependency>
>  <dependency>
>  <groupId>org.apache.camel.springboot</groupId>
>  <artifactId>camel-jackson-starter</artifactId>
>  </dependency>
>  <dependency>
>  <groupId>org.apache.camel.springboot</groupId>
>  <artifactId>camel-jaxb-starter</artifactId>
>  </dependency>
>  <dependency>
>  <groupId>org.apache.camel.springboot</groupId>
>  <artifactId>camel-metrics-starter</artifactId>
>  </dependency>
>  <dependency>
>  <groupId>org.apache.camel.springboot</groupId>
>  <artifactId>camel-soap-starter</artifactId>
>  </dependency>
>  <dependency>
>  <groupId>org.apache.camel.springboot</groupId>
>  <artifactId>camel-disruptor-starter</artifactId>
>  </dependency>{code}
>  
> Each of these starters now bring me the _spring-boot-starter-logging_ which I don't need as I'm using Log4J2 for this. As a result I have now both _log4J2_ and _logback_ in my classpath. Obviously I can add exclusions but then what's the point of the starters?
> Unless there's something subtle which I don't understand yet, I find the starters to be really targeting the lazy; I fail to see why is not enough to add _camel-spring-boot-starter_ for the purpose of having Spring Boot and next just add the regular Apache Camel's components?
> Ok, if starters are a nice to have thing, is it ok then to ignore them and simply add the regular Camel components to avoid this extra work? Can this be documented?
>  
> Thank you
>  



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