Details
-
Wish
-
Status: Resolved
-
Minor
-
Resolution: Invalid
-
3.4.0
-
None
-
None
-
Unknown
Description
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:
<!-- 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>
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