Antora xref checks and Antora repository dependencies

[Peter Palaga <pp...@redhat.com>]

Hi Zoran and other Antora experts,

In Camel Quarkus, we recently encountered some antora/xref-validator 
failures after a component was removed from Camel - see 
https://github.com/apache/camel-quarkus/issues/2109

As a fix, I made the Camel Quarkus Antora docs to depend on the 3.7.x 
branch of Camel https://github.com/apache/camel-quarkus/issues/2109

In that way removing components from Camel master cannot break Camel 
Quarkus master CI. I think in the future any upgrades of Camel in our 
Antora config should be done together with upgrading Camel in Maven.

I realize this kind of fix works well for us in Camel Quarkus, but may 
fail when Camel Quarkus is pulled by camel-website, if the Camel branch 
our master docs depends on, is not configured in the camel-website 
antora config.

So I'd like to ask, whether we could adopt the policy that the lastest 
Camel release always has a branch forked, and that that branch'es docs 
is published on Camel website regardless whether the branch is LTS or 
not. WDYT?

Thanks,

-- Peter

Re: Antora xref checks and Antora repository dependencies

[Peter Palaga <pp...@redhat.com>]

On 11/01/2021 11:47, Zoran Regvart wrote:
> Hi Peter,
> 
> On Fri, Jan 8, 2021 at 5:06 PM Peter Palaga <pp...@redhat.com> wrote:
>> So I'd like to ask, whether we could adopt the policy that the lastest
>> Camel release always has a branch forked, and that that branch'es docs
>> is published on Camel website regardless whether the branch is LTS or
>> not. WDYT?
> 
> My understanding is that we do that now. Currently we do not have a
> non-LTS release that we publish, that would be 3.8.x.. For Camel core
> we publish latest 2.x, last two 3.x LTS releases (3.4.x and 3.7.x),
> last 3.x release (would be 3.8.x) and latest from master (latest)

All is fine if this is the current state. I did not know 3.8.x would 
have its own docs published. Thanks for explaining!

-- Peter

Re: Antora xref checks and Antora repository dependencies

[Zoran Regvart <zo...@regvart.com>]

Hi Peter,

On Fri, Jan 8, 2021 at 5:06 PM Peter Palaga <pp...@redhat.com> wrote:
> So I'd like to ask, whether we could adopt the policy that the lastest
> Camel release always has a branch forked, and that that branch'es docs
> is published on Camel website regardless whether the branch is LTS or
> not. WDYT?

My understanding is that we do that now. Currently we do not have a
non-LTS release that we publish, that would be 3.8.x.. For Camel core
we publish latest 2.x, last two 3.x LTS releases (3.4.x and 3.7.x),
last 3.x release (would be 3.8.x) and latest from master (latest)

Did I miss something?

zoran
-- 
Zoran Regvart