[
https://issues.apache.org/jira/browse/SOLR-6661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185173#comment-14185173
]
Erik Hatcher commented on SOLR-6661:
------------------------------------
This has historically been a problem, and I've always adjusted the example
configurations when I build prototypes/demos to have this ${solr.install.dir}
system property concept. Now that we have start scripts, we can simply pass in
the already known Solr "install" (under which contrib/ lives, most importantly
for this issue) directory.
> 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
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
