Hi +1 This is great stuff.
So just think how would the developer do when eg you add a new component in the main Camel repo, lets call it components/camel-foobar ? Then you go to camel-spring-boot and want to generate a camel-foobar-starter because it should support SB too (Mind that not all components should have SB -starters). So it sounds like there is a new maven plugin you then use to generate all of that? Something a like: cd components-starter mvn camel-spring-boot-generator:prepare-spring-boot-starter -Dname=foobar Or how? We should have the steps documented in the readme file On Mon, Dec 9, 2019 at 10:47 PM Guillaume Nodet <gno...@apache.org> wrote: > > Hi everyone, > > Since Camel 3.0.0 has been released, and given we now have different > subprojects, I'd like to discuss the possibility of moving the spring boot > support into a different git repository. > I see several benefits: > * being able to support different versions of spring boot > * better decoupling > * improved build speed > I've created a PR at https://github.com/gnodet/camel/tree/CAMEL-14226 that > could be used for the new repo. I haven't tackled the PR for the main > camel repo yet, but it should be easier I think. > The internal tooling had to be adapted to cope with the new setup. The > main difference is that each starter uses a maven plugin which generates: > the starter pom, the spring boot configs and updates the catalog. > > Feedback welcomed ! > > Cheers, > Guillaume Nodet -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
