Hi Ah its some kind of chicken and egg, as the camel-quarkus guys to early upgraded in their end to point to camel 3.11.x docs. But we have not released 3.11 officially and published it to the website, so this causes that problem.
The solution is to find a way to publish "just once" the 3.11.0 release with docs on website, before upgrading that on quarkus side. Maybe we can remove the quarkus from the website build for just one build, and then add it back later. On Mon, Jun 28, 2021 at 9:55 AM Gregor Zurowski <gre...@list.zurowski.org> wrote: > > Hi Everyone: > > I am trying to finish releasing Camel 3.11.0, but we currently have > problems with the website build. There are 390 unresolved xrefs: > > === > repo: https://github.com/apache/camel-quarkus.git | branch: main | > component: camel-quarkus | version: latest > path: docs/modules/ROOT/pages/contributor-guide/extension-testing.adoc > | xref: 3.11.x@components::sql-component.adoc > path: docs/modules/ROOT/pages/index.adoc | xref: > 3.11.x@components::index.adoc > [...] > === > > (see > https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/240/console) > > Any idea how to fix this? > > Thanks in advance > Gregor -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
