Re: Closing down to Apache Camel 3.0 GA

Having another circuitBreaker implementation available in Camel would be great, as Hystrix is no longer in active development (see: https://github.com/Netflix/Hystrix#hystrix-status). Maybe Hystrix should even be deprecated. Am 14.11.2019 um 17:08 schrieb Claus Ibsen: Hi I have created a

Re: Requesting your help about Gsheets component

Sure Zoran, i will try to complete it and then share it with you. Thanks for your help! On Thu, 14 Nov 2019 at 12:06, Zoran Regvart wrote: > Hi Pablo, > we don't have a ready made example, if you haven't you can have a look > at the documentation[1] and examine the component tests[2]. > > If

Re: Requesting your help about Gsheets component

Hi Pablo, we don't have a ready made example, if you haven't you can have a look at the documentation[1] and examine the component tests[2]. If in your exploration you do end up creating an example and you'd like to share with us, please do create a pull request we could really use an example.

Requesting your help about Gsheets component

Hi guys, can you please shared with me an example about Gsheets component? Thanks!

Re: Closing down to Apache Camel 3.0 GA

Hi I have created a ticket about making hystrix EIP neutral as circuitBreaker() so we can plugin different implementations https://issues.apache.org/jira/browse/CAMEL-14182 This would be great to get done for 3.0 GA. I will start on this tomorrow. On Mon, Oct 28, 2019 at 3:39 PM Claus Ibsen

Re: [VOTE] Release Apache Camel K 1.0.0-M4 and Runtime 1.0.7

+1 (binding) Regards JB On 13/11/2019 16:19, Nicola Ferraro wrote: > Hello all: > > This is a combined vote to release Apache Camel K 1.0.0-M4 and Apache Camel > K Runtime 1.0.7. > > This is the first release of Camel K containing support for Camel Quarkus > (0.3.1 - JVM mode), > as explained

Re: [VOTE] Release Apache Camel K 1.0.0-M4 and Runtime 1.0.7

+1 (binding) On Wed, Nov 13, 2019 at 4:19 PM Nicola Ferraro wrote: > > Hello all: > > This is a combined vote to release Apache Camel K 1.0.0-M4 and Apache Camel > K Runtime 1.0.7. > > This is the first release of Camel K containing support for Camel Quarkus > (0.3.1 - JVM mode), > as explained

[GitHub] [camel-website] omarsmak commented on issue #108: CAMEL-13817: Change Getting Started links

omarsmak commented on issue #108: CAMEL-13817: Change Getting Started links URL: https://github.com/apache/camel-website/pull/108#issuecomment-553843793 No problem! Happy to help :) This is an automated message from the

[GitHub] [camel-website] zregvart merged pull request #108: CAMEL-13817: Change Getting Started links

zregvart merged pull request #108: CAMEL-13817: Change Getting Started links URL: https://github.com/apache/camel-website/pull/108 This is an automated message from the Apache Git Service. To respond to the message, please

[GitHub] [camel-website] zregvart commented on issue #108: CAMEL-13817: Change Getting Started links

zregvart commented on issue #108: CAMEL-13817: Change Getting Started links URL: https://github.com/apache/camel-website/pull/108#issuecomment-553843551 Thanks @omarsmak! This is an automated message from the Apache Git

[GitHub] [camel-website] zregvart commented on issue #108: CAMEL-13817: Change Getting Started links

zregvart commented on issue #108: CAMEL-13817: Change Getting Started links URL: https://github.com/apache/camel-website/pull/108#issuecomment-553843240 Preview here: https://builds.apache.org/job/Camel.website/job/PR-108/Preview/

[GitHub] [camel-website] zregvart commented on issue #108: CAMEL-13817: Change Getting Started links

zregvart commented on issue #108: CAMEL-13817: Change Getting Started links URL: https://github.com/apache/camel-website/pull/108#issuecomment-553836425 One last one (I hope):

[GitHub] [camel-website] omarsmak commented on issue #108: CAMEL-13817: Change Getting Started links

omarsmak commented on issue #108: CAMEL-13817: Change Getting Started links URL: https://github.com/apache/camel-website/pull/108#issuecomment-553833463 @zregvart actually I was doing `yarn build` always. Somehow I got the checks to work, I had to delete the generated `public` folder and

Re: [VOTE] Release Apache Camel K 1.0.0-M4 and Runtime 1.0.7

+1 (binding) Il mer 13 nov 2019, 16:19 Nicola Ferraro ha scritto: > Hello all: > > This is a combined vote to release Apache Camel K 1.0.0-M4 and Apache Camel > K Runtime 1.0.7. > > This is the first release of Camel K containing support for Camel Quarkus > (0.3.1 - JVM mode), > as explained in

Re: [VOTE] Release Apache Camel K 1.0.0-M4 and Runtime 1.0.7

+1 (binding) zoran On Wed, Nov 13, 2019 at 4:19 PM Nicola Ferraro wrote: > > Hello all: > > This is a combined vote to release Apache Camel K 1.0.0-M4 and Apache Camel > K Runtime 1.0.7. > > This is the first release of Camel K containing support for Camel Quarkus > (0.3.1 - JVM mode), > as

[GitHub] [camel-website] zregvart commented on issue #108: CAMEL-13817: Change Getting Started links

zregvart commented on issue #108: CAMEL-13817: Change Getting Started links URL: https://github.com/apache/camel-website/pull/108#issuecomment-553809029 @omarsmak did you run the build first (`yarn build)? We trust in the website CI build to catch the broken links. I misread,

[GitHub] [camel-website] omarsmak commented on issue #108: CAMEL-13817: Change Getting Started links

omarsmak commented on issue #108: CAMEL-13817: Change Getting Started links URL: https://github.com/apache/camel-website/pull/108#issuecomment-553795269 @bedlaj thanks a lot, I forgot that I can now actually restart the builds :). @zregvart actually this file was also changed by this PR

[GitHub] [camel-website] zregvart commented on issue #108: CAMEL-13817: Change Getting Started links

zregvart commented on issue #108: CAMEL-13817: Change Getting Started links URL: https://github.com/apache/camel-website/pull/108#issuecomment-553775304 Yeah, we have a check for broken links, this needs to be updated also: