[
https://issues.apache.org/jira/browse/SOLR-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620415#comment-13620415
]
Jan Høydahl commented on SOLR-4653:
-----------------------------------
[~dweiss] logging proposal is ok.
However, a better way would be to fail hard (can be made back-compat by
checking luceneMatchVersion and log only for <4.3). In that case how we include
contrib libs should change somehow. Perhaps something like this:
{code}
<lib>${solr.contrib.root}/extraction/lib</lib>
{code}
If user supplies -Dsolr.contrib.root=/path/to/contrib then stuff will work. If
nothing is passed by opts we could default to something that would work for the
shipped example config.
Also see my proposal in SOLR-4495. For most of my multi-core deploys I don't
bother adding lib entries to all cores, but use a single
sharedLib=$\{solr.solr.home\}/lib in solr.xml. Allowing multiple sharedLib dirs
in solr.xml would allow for more flexible config.
> Solr configuration should log inaccessible/ non-existent relative paths <lib
> dir="...">
> ---------------------------------------------------------------------------------------
>
> Key: SOLR-4653
> URL: https://issues.apache.org/jira/browse/SOLR-4653
> Project: Solr
> Issue Type: Bug
> Reporter: Dawid Weiss
> Assignee: Dawid Weiss
> Priority: Trivial
> Attachments: SOLR-4653.patch
>
>
> Currently the dir path is resolved relative to core's instanceDir but if you
> don't know it nothing happens (no warning, no nothing). This is very
> frustrating.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
