[
https://issues.apache.org/jira/browse/SOLR-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617278#comment-13617278
]
Dawid Weiss commented on SOLR-4653:
-----------------------------------
I am leaning towards throwing an exception too. A warning should be emitted if
the lib doesn't collect any jars (because that's odd too) but if it points at
void it looks like an error and in most cases (experienced on my own) what
follows is a class-not-found exception because something is referenced that
should be loaded and wasn't.
I agree with Yonik though that it'd be nice to be able to reference based from
solr's install dir. But then this may be problematic if people deploy the war
in other containers (I know, I know, it's a boo-hoo, but many people do it
anyway).
> 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]
