Hi
I do like how it is today where there is a -starter for each Camel
component we support on Spring Boot. That makes it easy to see what we
support and have.
Spring Boot v1.5 is the last 1.x release. Spring Boot is not like an
app server like Tomcat, JBoss etc where you host many apps in that ap
Hi Cameleers,
I'm wondering if it would be simpler to combine all starters into a
single artifact and what would the downside of that be?
So instead of having a number of *-starter artifacts, we could bundle
all *AutoConfiguration classes in camel-spring-boot-starter artifact
and guard them with @