[
https://issues.apache.org/jira/browse/SOLR-10616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045126#comment-16045126
]
Cassandra Targett commented on SOLR-10616:
------------------------------------------
bq. the full Solr version, like "6.6.0", for things like the binary package
I figured out another way around this, so we can live without it to avoid
confusion.
bq. the version with an underscore, like "6_6", to automate the sitemap.xml
generation
I have what I need for this ^^, but we still want some of the other items like
ZK version, etc., mentioned in the original description.
> use more ant variables in ref guide pages: particular for javadoc &
> third-party lib versions
> --------------------------------------------------------------------------------------------
>
> Key: SOLR-10616
> URL: https://issues.apache.org/jira/browse/SOLR-10616
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation
> Reporter: Hoss Man
>
> we already use ant variables for the lucene/solr version when building
> lucene/solr javadoc links, but it would be nice if we could slurp in the JDK
> javadoc URLs for the current java version & the versions.properties values
> for all third-party deps as well, so that links to things like the zookeeper
> guide, or the tika guide, or the javadocs for DateInstance would always be
> "current"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
