[
https://issues.apache.org/jira/browse/SOLR-15926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479721#comment-17479721
]
Cassandra Targett commented on SOLR-15926:
------------------------------------------
You know [~houston], we could leave this for now and fix it via Antora. Since
the version is a core attribute of every document, it's accessible internally
during build time as an inherent attribute
(https://docs.antora.org/antora/latest/page/intrinsic-attributes/#page-attributes).
I was trying to parse the version from the branch name, but Jenkins doesn't
like it so we need to explicitly define the version, which is done in the
branch now:
https://github.com/apache/solr/blob/jira/solr-15556-antora/solr/solr-ref-guide/antora.yml#L6.
I tested it with one attribute and it works fine - WDYT?
> Fix version specification in the Solr Ref Guide
> -----------------------------------------------
>
> Key: SOLR-15926
> URL: https://issues.apache.org/jira/browse/SOLR-15926
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation
> Affects Versions: 9.0
> Reporter: Houston Putman
> Priority: Blocker
> Fix For: 9.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently many places use the docs version (major.minor) with .0 added to the
> end, when we can easily just use the full solr version instead.
> There are also instances where the Solr version is used for the lucene
> version. This needs to be updated now that the two cannot be conflated.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
