On Thu, Nov 11, 2021 at 2:45 PM Zoran Regvart wrote:
>
> Hi Cameleers,
>
> On Thu, Nov 11, 2021 at 2:38 PM David Jencks wrote:
>
> > -The best way to show how the idempotency feature works, in
> > camel-kafka-connector, it's through an example. We'll use the [AWS2-S3
> > Source
> > connector](
About sending email about ci build of website failures on dev ML, I would use a
different address, because in the past we had complains about too much emails
or too much traffic from users.
--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apach
Hi Cameleers,
On Thu, Nov 11, 2021 at 2:38 PM David Jencks wrote:
> -The best way to show how the idempotency feature works, in
> camel-kafka-connector, it's through an example. We'll use the [AWS2-S3 Source
> connector](/camel-kafka-connector/next/reference/connectors/camel-aws2-s3-kafka-sour
I believe Andrea fixed this yesterday with
9c6826e7aad0119fb4c01925cf4bfc72e39114d7 (ckc). My PRs also fix it.
There’s another problem that will show up in the blog, which can be fixed with
this patch from https://github.com/apache/camel-website/pull/667:
diff --git a/content/blog/2020/12/CKC
Tested with CiA2 source code and this looks good
On Wed, Nov 10, 2021 at 5:08 PM Claus Ibsen wrote:
>
> +1 (binding)
>
> On Tue, Nov 9, 2021 at 8:09 AM Gregor Zurowski
> wrote:
> >
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 3.13.0, a new release with 119
> > new features an
+1 (non binding)
Thanks a lot Nicola!
> On 10 Nov 2021, at 13:27, Nicola Ferraro wrote:
>
> Hello all:
>
> This is a combined vote to release Apache Camel K 1.7.0, Camel K Runtime
> 1.10.0 and Kamelets 0.5.0.
>
> This is a major release based on Camel-Quarkus 2.4.0 and Camel 3.12.0 and
> cont
Hi Cameleers,
can someone (Andrea T.?) have a look at the broken xrefs in Camel
Kafka Connector?
This is reported on the website build[1]:
➤ YN:
{"level":"error","time":1636576185286,"name":"asciidoctor","file":{"path":"docs/modules/ROOT/pages/reference/index.adoc"},"source":{"url":"https://
Hi,
I was looking at why our CI missed the obvious problem on the
DirectVmProducerBlockingTest causing the core tests to hang.
I found 2 problems contributing to this which I would like to comment about
and bring to our attention.
Looking at the last known good build [1] we can see that there we
