You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Zoran Regvart <zo...@regvart.com> on 2021/11/11 09:34:34 UTC
Broken xrefs in Camel Kafka Connector
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]:
➤ YN0000: {"level":"error","time":1636576185286,"name":"asciidoctor","file":{"path":"docs/modules/ROOT/pages/reference/index.adoc"},"source":{"url":"https://github.com/apache/camel-kafka-connector.git","refname":"main","startPath":"docs"},"msg":"target
of xref not found:
reference/connectors/camel-syslog-kafka-sink-connector.adoc"}
➤ YN0000: {"level":"error","time":1636576185288,"name":"asciidoctor","file":{"path":"docs/modules/ROOT/pages/reference/index.adoc"},"source":{"url":"https://github.com/apache/camel-kafka-connector.git","refname":"main","startPath":"docs"},"msg":"target
of xref not found:
reference/connectors/camel-syslog-kafka-source-connector.adoc"}
➤ YN0000: {"level":"error","time":1636576213845,"name":"asciidoctor","file":{"path":"docs/modules/ROOT/nav.adoc"},"source":{"url":"https://github.com/apache/camel-kafka-connector.git","refname":"main","startPath":"docs"},"msg":"target
of xref not found:
reference/connectors/camel-syslog-kafka-source-connector.adoc"}
➤ YN0000: {"level":"error","time":1636576213846,"name":"asciidoctor","file":{"path":"docs/modules/ROOT/nav.adoc"},"source":{"url":"https://github.com/apache/camel-kafka-connector.git","refname":"main","startPath":"docs"},"msg":"target
of xref not found:
reference/connectors/camel-syslog-kafka-sink-connector.adoc"}
So the index.adoc has links to several connectors that don't seem to resolve.
zoran
[1] https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/523/console
--
Zoran Regvart
Re: Broken xrefs in Camel Kafka Connector
Posted by Claus Ibsen <cl...@gmail.com>.
On Thu, Nov 11, 2021 at 2:45 PM Zoran Regvart <zo...@regvart.com> wrote:
>
> Hi Cameleers,
>
> On Thu, Nov 11, 2021 at 2:38 PM David Jencks <da...@gmail.com> 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-source-connector.html)
> > +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/0.11.0/reference/connectors/camel-aws2-s3-kafka-source-connector.html)
>
> Yeah, we need to reference concrete versions, there is no guarantee
> that a page will be present in the future. Though there is also no
> guarantee that it will be present from a concrete version once we stop
> building that version. Not sure what a good option would be here.
>
> > On a more general note, can we make jenkins website build failures email the dev list? I have too hard a time detecting these problems. It seems that I get plenty of emails from GH actions about other build failures, surely the website is as important.
>
> +1 I can have a look at this
>
-1 agree with Andrea we want @dev to be human only emails so it's easy
to follow topics there. In the past we had automated emails and it
spammed this list.
You can use another mailing list such as issues or we can create a new
one for such purpose.
> zoran
> --
> Zoran Regvart
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Broken xrefs in Camel Kafka Connector
Posted by Andrea <an...@tarocch.it>.
+1
On Fri, Nov 12, 2021, at 10:42, Andrea Cosentino wrote:
> Yes, I think it would be a good idea.
>
> Il giorno ven 12 nov 2021 alle ore 10:41 Zoran Regvart <zo...@regvart.com>
> ha scritto:
>
> > Hi Cameleers,
> >
> > On Fri, Nov 12, 2021 at 6:46 AM Andrea Cosentino
> > <an...@yahoo.com.invalid> wrote:
> > > 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.
> >
> > I've seen that Camel Quarkus subprojects creates GitHub issues for
> > failed builds, perhaps that would be a good way?
> >
> > zoran
> > --
> > Zoran Regvart
> >
>
Re: Broken xrefs in Camel Kafka Connector
Posted by Andrea Cosentino <an...@gmail.com>.
Yes, I think it would be a good idea.
Il giorno ven 12 nov 2021 alle ore 10:41 Zoran Regvart <zo...@regvart.com>
ha scritto:
> Hi Cameleers,
>
> On Fri, Nov 12, 2021 at 6:46 AM Andrea Cosentino
> <an...@yahoo.com.invalid> wrote:
> > 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.
>
> I've seen that Camel Quarkus subprojects creates GitHub issues for
> failed builds, perhaps that would be a good way?
>
> zoran
> --
> Zoran Regvart
>
Re: Broken xrefs in Camel Kafka Connector
Posted by Zoran Regvart <zo...@regvart.com>.
Hi Cameleers,
On Fri, Nov 12, 2021 at 6:46 AM Andrea Cosentino
<an...@yahoo.com.invalid> wrote:
> 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.
I've seen that Camel Quarkus subprojects creates GitHub issues for
failed builds, perhaps that would be a good way?
zoran
--
Zoran Regvart
Re: Broken xrefs in Camel Kafka Connector
Posted by Andrea Cosentino <an...@yahoo.com.INVALID>.
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
Apache Servicemix PMC Member
Email: ancosen1985@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Thursday, November 11, 2021, 02:45:48 PM GMT+1, Zoran Regvart <zo...@regvart.com> wrote:
Hi Cameleers,
On Thu, Nov 11, 2021 at 2:38 PM David Jencks <da...@gmail.com> 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-source-connector.html)
> +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/0.11.0/reference/connectors/camel-aws2-s3-kafka-source-connector.html)
Yeah, we need to reference concrete versions, there is no guarantee
that a page will be present in the future. Though there is also no
guarantee that it will be present from a concrete version once we stop
building that version. Not sure what a good option would be here.
> On a more general note, can we make jenkins website build failures email the dev list? I have too hard a time detecting these problems. It seems that I get plenty of emails from GH actions about other build failures, surely the website is as important.
+1 I can have a look at this
zoran
--
Zoran Regvart
Re: Broken xrefs in Camel Kafka Connector
Posted by Zoran Regvart <zo...@regvart.com>.
Hi Cameleers,
On Thu, Nov 11, 2021 at 2:38 PM David Jencks <da...@gmail.com> 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-source-connector.html)
> +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/0.11.0/reference/connectors/camel-aws2-s3-kafka-source-connector.html)
Yeah, we need to reference concrete versions, there is no guarantee
that a page will be present in the future. Though there is also no
guarantee that it will be present from a concrete version once we stop
building that version. Not sure what a good option would be here.
> On a more general note, can we make jenkins website build failures email the dev list? I have too hard a time detecting these problems. It seems that I get plenty of emails from GH actions about other build failures, surely the website is as important.
+1 I can have a look at this
zoran
--
Zoran Regvart
Re: Broken xrefs in Camel Kafka Connector
Posted by David Jencks <da...@gmail.com>.
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-idempotency-070/index.md b/content/blog/2020/12/CKC-idempotency-070/index.md
index 4d25f25caa..da4cb5c81e 100644
--- a/content/blog/2020/12/CKC-idempotency-070/index.md
+++ b/content/blog/2020/12/CKC-idempotency-070/index.md
@@ -66,7 +66,7 @@ Some of the options can be used with their default value, in this example we're
### A real example
-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-source-connector.html)
+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/0.11.0/reference/connectors/camel-aws2-s3-kafka-source-connector.html)
As first step you'll need to fully build the [Camel-Kafka-connector project](https://github.com/apache/camel-kafka-connector) and install the connectors/camel-aws2-s3-kafka-connector zip package in your Kafka Broker plugin.path. Once the connector is in the plugin.path location, just unzip it. We describe how to build and unpack in the next steps:
This isn’t going to work for long, since the page referenced is no longer in the next documentation, so will eventually disappear from the released branch, even if we had a way to keep the specific release version correct.
I don’t have a solution in mind for this problem.
On a more general note, can we make jenkins website build failures email the dev list? I have too hard a time detecting these problems. It seems that I get plenty of emails from GH actions about other build failures, surely the website is as important.
David Jencks
> On Nov 11, 2021, at 1:34 AM, Zoran Regvart <zo...@regvart.com> wrote:
>
> 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]:
>
> ➤ YN0000: {"level":"error","time":1636576185286,"name":"asciidoctor","file":{"path":"docs/modules/ROOT/pages/reference/index.adoc"},"source":{"url":"https://github.com/apache/camel-kafka-connector.git","refname":"main","startPath":"docs"},"msg":"target
> of xref not found:
> reference/connectors/camel-syslog-kafka-sink-connector.adoc"}
> ➤ YN0000: {"level":"error","time":1636576185288,"name":"asciidoctor","file":{"path":"docs/modules/ROOT/pages/reference/index.adoc"},"source":{"url":"https://github.com/apache/camel-kafka-connector.git","refname":"main","startPath":"docs"},"msg":"target
> of xref not found:
> reference/connectors/camel-syslog-kafka-source-connector.adoc"}
> ➤ YN0000: {"level":"error","time":1636576213845,"name":"asciidoctor","file":{"path":"docs/modules/ROOT/nav.adoc"},"source":{"url":"https://github.com/apache/camel-kafka-connector.git","refname":"main","startPath":"docs"},"msg":"target
> of xref not found:
> reference/connectors/camel-syslog-kafka-source-connector.adoc"}
> ➤ YN0000: {"level":"error","time":1636576213846,"name":"asciidoctor","file":{"path":"docs/modules/ROOT/nav.adoc"},"source":{"url":"https://github.com/apache/camel-kafka-connector.git","refname":"main","startPath":"docs"},"msg":"target
> of xref not found:
> reference/connectors/camel-syslog-kafka-sink-connector.adoc"}
>
> So the index.adoc has links to several connectors that don't seem to resolve.
>
> zoran
>
> [1] https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/523/console
> --
> Zoran Regvart