The steps to perform when adding / removing a new camel component are still to be defined. Currently, what is working is the update of existing starters. I think creating two goals to add / remove a starter can be easily done, so that i could be done in an easy step. I'll work on that. I've also spotted that the BOM generation isn't fully updated with the new proposed source layout, so I'll fix it first.
Guillaume Le mar. 10 déc. 2019 à 10:19, Zoran Regvart <zo...@regvart.com> a écrit : > Hi Guillaume, > +1 for the effort, I very much appreciate any effort to > simplify/speedup the build and separate the concerns. > > I would also like to know how the workflow for keeping the starters in > sync would look like, would this be done by individually: on changes > to the Camel repository there needs to be a corresponding change in > the Camel Spring Boot repository? Could we invest in some automation > here? > > zoran > > 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 > > > > -- > Zoran Regvart > -- ------------------------ Guillaume Nodet
