Hi Everyone: I wanted to follow up on Andrea's question regarding the release process. As Guillaume already pointed out, one of the benefits of splitting Spring Boot support into a separate repository is to be able to support multiple Spring Boot versions. This would mean that the Spring Boot support artifacts will have a separate release cycle? If this is the case, I believe it's extremely important to provide an overview that shows which Camel version works with which Spring Boot support artifacts.
Thanks, Gregor On Tue, Dec 10, 2019 at 8:11 AM Andrea Cosentino <ancosen1...@yahoo.com.invalid> wrote: > > Really good work! > > I think this is just the first step, we can use a similar approach for the > others flavours. > > But we need to document everything really well and we need to rethink about > the release process, I guess. > > Thanks! > > -- > Andrea Cosentino > ---------------------------------- > Apache Camel PMC Chair > Apache Karaf Committer > Apache Servicemix PMC Member > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github: oscerd > > > > > > > On Monday, December 9, 2019, 10:47:55 PM GMT+1, 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
