[ 
https://issues.apache.org/jira/browse/CAMEL-12246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358412#comment-16358412
 ] 

ASF GitHub Bot commented on CAMEL-12246:
----------------------------------------

fbolton commented on issue #2215: CAMEL-12246 Fix broken links
URL: https://github.com/apache/camel/pull/2215#issuecomment-364439529
 
 
   @oscerd yes, but I have the impression that most links were already broken 
in GitHub anyway. For example, if you look at the camel-http doc page in the 
commit *before* this PR was merged:
   
https://github.com/apache/camel/blob/ee26d31bcc10fad113fa46cbf0bf4b36f9f0cfbc/components/camel-http/src/main/docs/http-component.adoc
   
   Search for the link to "Jetty Component". When you click on it, you get a 
404. My impression is that this is fairly typical of the links that were 
already there.

----------------------------------------------------------------
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:
us...@infra.apache.org


> 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
>            Assignee: Andrea Cosentino
>            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
(v7.6.3#76005)

Reply via email to