[
https://issues.apache.org/jira/browse/SOLR-6661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher resolved SOLR-6661.
--------------------------------
Resolution: Fixed
Fix Version/s: Trunk
Also added this to bin/solr.cmd for Windows as well (someone please test).
> Address relative path <lib> references
> --------------------------------------
>
> Key: SOLR-6661
> URL: https://issues.apache.org/jira/browse/SOLR-6661
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.10
> Reporter: Erik Hatcher
> Assignee: Erik Hatcher
> Priority: Critical
> Fix For: 5.0, Trunk
>
> Attachments: SOLR-6661.patch
>
>
> Relative paths in solrconfig.xml's <lib> references are wrong, and require
> manual adjusting, when the base directory moves to different place in the
> file system tree. This can happen when cloning a configuration, such as the
> new start scripts in "-e cloud" mode.
> Having an incorrect relative path manifests itself as /browse not working
> (can't find VelocityResponseWriter related JARs), and likewise with
> /update/extract because of wrong paths to Tika, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
