ASF GitHub Bot commented on CAMEL-12246:

fbolton opened a new pull request #2215: CAMEL-12246 Fix broken links
URL: https://github.com/apache/camel/pull/2215
   @davsclaus and @oscerd, here are the changes to the AsciiDoc linking that we 
discussed. Here's a summary of what was done:
   * Resolve the duplicate IDs (can't do any harm, and is actually required for 
our downstream builds)
   * Take into account the -eip suffix, which might reduce the number of 
unresolved links.
   * All resolvable links to be transformed to AsciiDoc cross-reference format, 
as follows:
   link:LINKNAME.html[Text of Link]  =>  <<LINKNAME, Text of Link>>
     Where, in some cases, `LINKNAME` might be augmented by a `-component`, 
`-dataformat`, `-language`, or `-eip` suffix.
   * Identify the broken EIP links and leave them alone. These will continue to 
show up as broken links, but we can easily fix them later.
   * All other unresolved links will be removed. Probably do this by replacing:
   link:LINKNAME.html[Text of Link]   =>  Text of Link

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> New AsciiDoc documentation has many broken links
> ------------------------------------------------
>                 Key: CAMEL-12246
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12246
>             Project: Camel
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 2.21.0
>            Reporter: Fintan Bolton
>            Priority: Major
>             Fix For: 2.21.0
> There are a fair number of broken links in the new AsciiDoc documentation (in 
> the main Camel repo). In other words, links like {{link:LINKNAME.html[Link 
> Text]}} ought to have a matching target ID, {{[[LINKNAME]]}}, in the AsciiDoc 
> source. But I found 245 LINKNAMEs in links that have no corresponding target 
> ID defined.

This message was sent by Atlassian JIRA

Reply via email to