[
https://issues.apache.org/jira/browse/SOLR-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617253#comment-13617253
]
Erick Erickson commented on SOLR-4653:
--------------------------------------
What! And take the sensitive, appropriate-for-your-aged-grandmother notes out
of solrconfig.xml? To whit:
<!-- If a 'dir' option (with or without a regex) is used and nothing
is found that matches, it will be ignored
-->
<lib dir="/total/crap/dir/ignored" />
<G>....
Which is more than a little inconsistent with what follows:
<!-- an exact 'path' can be used instead of a 'dir' to specify a
specific jar file. This will cause a serious error to be logged
if it can't be loaded.
-->
<!--
<lib path="../a-jar-that-does-not-exist.jar" />
-->
Why should failing to find a specific jar log a serious error but a directory
be ignored?
Seriously, let's complain if the dir isn't found, at least log a warning if not
an error/exception. Fail early, fail often.
> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
