[
https://issues.apache.org/jira/browse/SOLR-10616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16472756#comment-16472756
]
Hoss Man commented on SOLR-10616:
---------------------------------
{quote}The parameters are all in the {{_config.yml.template}} file.
{quote}
NOTE: they also have to be put in the corrisponding section of build.xml so
they work in the PDF build (eventually i'd like to write our own ant
task/hook/launcher so we can just keep them all in one place, and verify that
they aren't blank/unset – which is currently a risk if someone changes the
variable names in the ivy-versions.properties file)
> 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
> Assignee: Hoss Man
> Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: SOLR-10616.patch
>
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
