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

Cassandra Targett commented on SOLR-12786:
------------------------------------------

Yes, we need to move up at some point. Ideas on how to enforce/check for the 
Asciidoctor version are welcome.

>From the discuss.asciidoctor.org thread I pointed to, the 2nd variation of the 
>problem is the one that will cause us some ongoing issues - if you look at a 
>page like {{format-of-solr.html}}, the change makes it somewhat non-intuitive 
>on how links are constructed. AFIAK, the only way to force a link format is to 
>manually put anchors on every section, which I strive to avoid because it 
>complicates making correct links in other ways. 

Overall, I'm sorry about this; I thought I'd filed an issue about the version 
requirement, but see from the commit I did not. That time period in May was 
very hectic for me, so after spending a couple hours figuring out what was 
wrong and then deciding what to do about it, I probably  then had to move on to 
something else and subsequently forgot about filing an issue.

> HTML reference guide has invalid links
> --------------------------------------
>
>                 Key: SOLR-12786
>                 URL: https://issues.apache.org/jira/browse/SOLR-12786
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: documentation
>    Affects Versions: master (8.0)
>            Reporter: Jan Høydahl
>            Priority: Major
>         Attachments: SOLR-12786.patch
>
>
> The refguide build aborts due to this.
> Example: "updating-solr-s-include-files" should instead be 
> "updating-solrs-include-files" since apostrophe is not replaced with dash.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to