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

Hoss Man commented on SOLR-12118:
---------------------------------

Attached patch adds 7 new attributes to our ref-guide build for the 7 diff 
libraries i could find whose version is explicitly mentioned in some way in the 
docs...
 * commons-codec
 * dropwizard
 * log4j
 * opennlp
 * tika
 * velocity
 * zookeeper

In most cases, these mentions were in URLs linking to documentation – but that 
may be a Streetlight Effect since searching the source files for URLs that 
looked like they had version numbers was easy – there are probably other third 
party version mentions in "plain text" that i have overlooked.

Fortunately adding more variables like this is easy.

> use ivy-versions.properties values as attributes in ref-guide files to 
> replace hard coded version numbers
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-12118
>                 URL: https://issues.apache.org/jira/browse/SOLR-12118
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Hoss Man
>            Assignee: Hoss Man
>            Priority: Major
>         Attachments: SOLR-12118.patch
>
>
> There's currently a bunch of places in the ref guide where we mention third 
> party libraries and refer to hard coded version numbers - many of which are 
> not consistent with the versions of those libraries actually in use because 
> it's easy to overlook them.
> We should improve the ref-guide build files to pull in the 
> {{ivy-version.properties}} variables to use as attributes in the source files.



--
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