I can do that :-) but it doesn’t answer my question of what the camel-quarkus
version refers to. Is it arbitrary? Does it refer to a quarkus version?
If it refers to a quarkus version then I think the display version for latest
ought to be something like 2.3.0 (Pre-release). In any case I suspect latest
should be labeled prerelease.
What is the relationship between camel-quarkus and camel? There are some hints
in the antora.yml component descriptors that both 2.0.0 and latest use camel
3.11.x. What’s going to happen when 3.12.0 is released?
I think this version correspondence to quarkus and camel should be documented
at least in the camel-quarkus README.adoc and preferebly somewhere in the docs
themselves as well. For instance,
```
This version of camel-quarkus uses quarkus {quarkus-version} and camel
{camel-version}.
```
David Jencks
> On Sep 22, 2021, at 10:31 PM, Claus Ibsen <claus.ib...@gmail.com> wrote:
>
> Hi
>
> Ah camel-quarkus likely haven't updated and removed outdated releases.
> Its latest release is 2.2.0, which should be there instead of 2.0.0.
> The 2.0.0 should be removed.
>
> On Thu, Sep 23, 2021 at 4:38 AM David Jencks <david.a.jen...@gmail.com> wrote:
>>
>> So camel-quarkus latest referring to camel components 3.11.x seems
>> reasonable. What about camel-quarkus 2.0.0?
>>
>> Now I noticed some more problems….
>>
>> I can’t figure out what the meaning of the camel-quarkus version is. What
>> does the `2.0.0` in the non-latest version refer to? What about `latest`?
>>
>> This is reflected in these pages….
>>
>> (1) https://camel.apache.org/camel-quarkus/2.0.0/reference/components.html
>> (2) https://camel.apache.org/camel-quarkus/2.0.0/reference/dataformats.html
>> (3) https://camel.apache.org/camel-quarkus/2.0.0/reference/languages.html
>> (4) https://camel.apache.org/camel-quarkus/2.0.0/reference/others.html
>>
>> the tables are constructed by attempting to query some parts of the main
>> camel components component. 1, 3, and 4 query at version `2.0.0` which, not
>> existing, produces no results. 2 queries at version `latest`
>>
>> Some of the attributes used in these queries should be in the antora.yml
>> component descriptor, but I’d like to understand what the correct values are
>> before putting them there.
>>
>> David Jencks
>>
>>> On Sep 18, 2021, at 12:31 AM, Zoran Regvart <zo...@regvart.com> wrote:
>>>
>>> Hi David & Cameleers,
>>> as far as I’m aware, all sub-projects lag behind the latest Camel version.
>>> I don’t know if that’s a problem, they usually are not very far behind.
>>> For the documentation and Camel Quarkus in particular, the past experience
>>> was that pointing to the latest Camel version often led to broken links so
>>> not changing the version led to greater stability of the website.
>>> I do think that documentation should be cross linked against the correct
>>> versions, i.e. the ones they depend on in the code and that version should
>>> be prominently displayed in the documentation.
>>>
>>> zoran
>>> --
>>> Sent from mobile
>>>
>>>> On 16. Sep 2021, at 22:10, David Jencks <david.a.jen...@gmail.com> wrote:
>>>>
>>>> While fixing the broken camel-quarkus partial website build I noticed a
>>>> couple of things I don’t understand.
>>>>
>>>> 1. camel-quarkus latest seems to use camel 3.11.x, at least the docs do.
>>>> I think that, if this is really correct, the camel-quarkus index page
>>>> should prominently say that you aren’t getting the cutting-edge latest
>>>> camel in camel-quarkus, but something slightly older. Naively, I expected
>>>> camel-quarkus versions to track camel versions. Indicating the
>>>> relationship between versions would certainly help me.
>>>>
>>>> 2. eips are now versioned with components, but at least some links from
>>>> components to eips use {eip-vc} in
>>>> xref:{eip-vc}:eips:polling-consumer.adoc[Polling Consumer]
>>>> which points to the latest eips. If camel-quarkus really intentionally
>>>> depends on camel 3.11.x then it should be possible to build the partial
>>>> website with only the 3.11.x versions, but I get lots of errors like
>>>>
>>>> [ERROR] [12:44:05.727] ERROR (asciidoctor): target of xref not found:
>>>> latest@components:eips:polling-consumer.adoc
>>>> [ERROR] file:
>>>> docs/components/modules/ROOT/pages/beanstalk-component.adoc
>>>> [ERROR] source: https://github.com/apache/camel.git (refname:
>>>> camel-3.11.x, start path: docs/components)
>>>>
>>>> I think there are 22 such usages, involving all links in the `components`
>>>> component to eips.
>>>>
>>>> If we agree this is a problem I’ll prepare some PRs for the affected
>>>> branches (presumably at least main and 3.11.x)
>>>>
>>>>
>>>> David Jencks
>>>>
>>>> side note: The camel-quarkus index page (both latest and 2.0.0) says
>>>> Camel Quarkus also takes advantage of the many performance improvements
>>>> made in Camel 3, which results in a lower memory footprint, less reliance
>>>> on reflection (which is good for native application support) and faster
>>>> startup times.
>>>> I’m bewildered by this, and want to know “compared with what?”. I also
>>>> think it would be nice if there was an explanation of what is different
>>>> between the latest and 2.0.0 versions of camel-quarkus, right on the index
>>>> page.
>>>>
>>>>
>>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
