You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Dawid Weiss (JIRA)" <ji...@apache.org> on 2013/04/02 16:49:16 UTC
[jira] [Updated] (SOLR-4653) Solr configuration should log
inaccessible/ non-existent relative paths
[ https://issues.apache.org/jira/browse/SOLR-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dawid Weiss updated SOLR-4653:
------------------------------
Attachment: SOLR-4653.patch
This is my take at this having considered a few other alternatives. It logs this at startup currently:
{code}
Can't find (or read) directory to add to classloader: /total/crap/dir/ignored (resolved as: C:\Work\lucene-solr-svn\trunk\solr\example\solr\collection1\total\crap\dir\ignored).
{code}
And indeed the example config contains:
{code}
<!-- 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" />
{code}
Perhaps the comment should be changed/ made more polite too.
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org