Hi Claudio,

I think the approach is fine. I also agree the change to Camel Quarkus can
make things easier for Camel K. Although I do have some concerns of
appropriateness of some code that now lies in Camel K runtime, I think it's
a matter of adjusting them to be more generic or moving them up or down to
Camel Core or Camel K as needed.

Anyway, I think it's a good idea. As far as I am concerned, it's a +1.

Thanks!


On Fri, Nov 18, 2022 at 2:34 PM Claus Ibsen <claus.ib...@gmail.com> wrote:

> Hi
>
> +1
> Yes this would be really good.
>
>
> On Thu, Nov 17, 2022 at 3:17 PM Claudio Miranda <clau...@claudius.com.br>
> wrote:
>
> > Hi, camel-k-runtime project was created to have several camel
> > components (and the related quarkus extensions) suitable for Camel K,
> > however all camel components are already into camel, and only the
> > quarkus extensions are in camel-k-runtime.
> >
> > Today we have to manage camel-k-runtime releases and align versions to
> > camel and camel-quarkus. Also from a Camel K perspective we currently
> > depend on camel-k-runtime and when we need a new fix provided by
> > either camel-quarkus or camel, we should have those versions aligned
> > in camel-k-runtime first.
> >
> > It seems appropriate to think about merging camel-k-runtime remaining
> > quarkus extensions into camel-quarkus. Having Camel K to depend only
> > on camel-quarkus would improve our development cadence and quicker
> > releases.
> >
> > And this is what I would like to propose and receive feedback.
> >
> > I see the current quarkus extensions in camel-k-runtime must be
> > tailored to follow camel-quarkus way and I will create a camel epic
> > task to outline the main points. All of this should be in a specific
> > branch for later review.
> >
> > So I would appreciate your feedback on this.
> >
> > Thanks
> > --
> >   Claudio Miranda
> >
> > clau...@claudius.com.br
> > http://www.claudius.com.br
> >
>
>
> --
> Claus Ibsen
> -----------------
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

Reply via email to