Le mar. 10 déc. 2019 à 10:35, Claus Ibsen <claus.ib...@gmail.com> a écrit :

> On Tue, Dec 10, 2019 at 10:19 AM Zoran Regvart <zo...@regvart.com> wrote:
> >
> > 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?
>
> I actually dont mind its not fully automated, as for example today we
> end up mistakenly generating -starter JARs
> from some stuff that does not work with SB or is not intended at all
> (eg another runtime like MP or OSGi).
> And then we need to go in an add code into the maven plugin to skip
> those which are hardcoded in the source.
>
> So I think its fine if its a step where you then go to the
> camel-spring-boot repo and then run a maven plugin that generate the
> -starter.
>

Right, that's what I did.
The commands are available at
https://github.com/gnodet/camel/tree/CAMEL-14226#creating--deleting-starters
and
do use a maven plugin underneath.


>
> With the Camel catalog we can/should generate a new page on the
> website that lists all the artifacts and has [x] for which runtimes
> they support.
> Then you can quickly see where there is gaps etc
> https://issues.apache.org/jira/browse/CAMEL-13804
>
>
Agreed, I'll see if something can be generated.

Afaik, I've fixed all the generation and tests, so the whole build works
fine now.
I'll work on the main camel repo now.

Guillaume


> >
> > 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
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
------------------------
Guillaume Nodet

Reply via email to