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

ASF subversion and git services commented on SOLR-12118:
--------------------------------------------------------

Commit 9c1f55b32a53be3b3b7cbf42c9799fa4360ad01a in lucene-solr's branch 
refs/heads/branch_7x from Chris Hostetter
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=9c1f55b ]

SOLR-12118: Solr Ref-Guide can now use some ivy version props directly as 
attributes in content

(cherry picked from commit d6ed71b5c4777db1847ae18f11855d853f511f40)

Conflicts:
        solr/CHANGES.txt


> 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