[
https://issues.apache.org/jira/browse/CAMEL-16228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286048#comment-17286048
]
David Jencks commented on CAMEL-16228:
--------------------------------------
I'm afraid I don't understand the problem yet. A couple of specific examples
would really help.
Meanwhile, some comments....
* If Camel (core), Spring Boot and Karaf are released in lockstep, I wonder if
it would be more appropriate to have them all parts of the same distributed
component. Basically, do you want the navigation tree to change when you go
say from a camel component to the spring boot info about it? I'd think it
might possibly be nicer to have the links to spring boot and karaf pages nested
under the link to the component page in the navigation.
* If you need all the links from say camel-quarkus version X to refer to camel
components version Y you can define an attribute in the camel-quarkus version X
antora.yml:
```
asciidoctor:
attributes:
camel-components-version: Y
```
and use that in your xref:
`href:\{camel-components-version}@components:languages:foo.adoc[]`
> Documentation: Fix xref link in old branches
> --------------------------------------------
>
> Key: CAMEL-16228
> URL: https://issues.apache.org/jira/browse/CAMEL-16228
> Project: Camel
> Issue Type: Task
> Components: documentation, website
> Reporter: Andrea Cosentino
> Priority: Major
> Fix For: 3.x
>
>
> Currently in the .adoc of our documentation we are using (for example)
> xref:components::kafka-component.adoc[KafkaIdempotentRepository]
> This is ok for master branch and latest documentation.
> The problem arises when we look at older active branch, all the link to
> components in 3.7.x for example are still pointi to latest. We need to change
> the docs in the following way
> xref:3.7.x@components::kafka-component.adoc[KafkaIdempotentRepository]
> We need to do this for 3.8.x, 3.7.x and 3.4.x
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
