Re: camel-k: switch to Quarkus as default framework for integrations

2020-06-10 Thread Luca Burgazzoli
Opened the following two issues: - https://github.com/apache/camel-k/issues/1513 - https://github.com/apache/camel-k-runtime/issues/359 --- Luca Burgazzoli On Mon, Jun 8, 2020 at 10:15 AM Otavio Rodolfo Piske wrote: > I think this is a good idea. > > +1 > > On Sat, Jun 6, 2020 at 7:57 AM

Re: camel-k: switch to Quarkus as default framework for integrations

2020-06-08 Thread Otavio Rodolfo Piske
I think this is a good idea. +1 On Sat, Jun 6, 2020 at 7:57 AM Claus Ibsen wrote: > +1 > > On Fri, Jun 5, 2020 at 1:45 PM Luca Burgazzoli > wrote: > > > > Hello everyone, > > > > When we started working on camel-k, we haven't found any > runtime/framework > > that could cope with the type of

Re: camel-k: switch to Quarkus as default framework for integrations

2020-06-07 Thread Alex Dettinger
+1 On Sat, Jun 6, 2020 at 11:53 AM Federico Valeri wrote: > +1 > > On Sat, Jun 6, 2020 at 7:57 AM Claus Ibsen wrote: > > > > +1 > > > > On Fri, Jun 5, 2020 at 1:45 PM Luca Burgazzoli > wrote: > > > > > > Hello everyone, > > > > > > When we started working on camel-k, we haven't found any >

Re: camel-k: switch to Quarkus as default framework for integrations

2020-06-06 Thread Federico Valeri
+1 On Sat, Jun 6, 2020 at 7:57 AM Claus Ibsen wrote: > > +1 > > On Fri, Jun 5, 2020 at 1:45 PM Luca Burgazzoli wrote: > > > > Hello everyone, > > > > When we started working on camel-k, we haven't found any runtime/framework > > that could cope with the type of workloads we had in mind for

Re: camel-k: switch to Quarkus as default framework for integrations

2020-06-05 Thread Claus Ibsen
+1 On Fri, Jun 5, 2020 at 1:45 PM Luca Burgazzoli wrote: > > Hello everyone, > > When we started working on camel-k, we haven't found any runtime/framework > that could cope with the type of workloads we had in mind for camel-k so we > ended up rolling our own framework but later on the Quarkus

Re: camel-k: switch to Quarkus as default framework for integrations

2020-06-05 Thread Luca Burgazzoli
On Fri, Jun 5, 2020 at 4:14 PM Zheng Feng wrote: > +1 But it looks like not all of the camel components have been available on > the camel-quarkus. Would this be a problem ? > I don't see this as a severe issue as it is just a matter of time and we can at least generate a JVM only extension of

Re: camel-k: switch to Quarkus as default framework for integrations

2020-06-05 Thread Zheng Feng
+1 But it looks like not all of the camel components have been available on the camel-quarkus. Would this be a problem ? On Fri, Jun 5, 2020 at 7:51 PM Luca Burgazzoli wrote: > Hello everyone, > > When we started working on camel-k, we haven't found any runtime/framework > that could cope with

Re: camel-k: switch to Quarkus as default framework for integrations

2020-06-05 Thread Andrea Cosentino
+1 on this, I believe it totally makes sense to default on quarkus. Il giorno ven 5 giu 2020 alle ore 14:58 Omar Al-Safi ha scritto: > +1 > I think IMHO it would make sense to rely on Quarkus since this is what > meant for. At the beginning, when I was getting into Camel-k, I was only >

Re: camel-k: switch to Quarkus as default framework for integrations

2020-06-05 Thread Omar Al-Safi
+1 I think IMHO it would make sense to rely on Quarkus since this is what meant for. At the beginning, when I was getting into Camel-k, I was only confused about the runtimes being used there, hence I think it would make sense to reduce the runtimes in order to allow greater focus. Regards, Omar

camel-k: switch to Quarkus as default framework for integrations

2020-06-05 Thread Luca Burgazzoli
Hello everyone, When we started working on camel-k, we haven't found any runtime/framework that could cope with the type of workloads we had in mind for camel-k so we ended up rolling our own framework but later on the Quarkus project has started and that has changed a little the landscape as the