Solr classpath is not setup correctly if core's instanceDir does not exist on
startup
-------------------------------------------------------------------------------------
Key: SOLR-2683
URL: https://issues.apache.org/jira/browse/SOLR-2683
Project: Solr
Issue Type: Bug
Components: multicore
Affects Versions: 4.0
Reporter: Yury Kats
When I launch Solr and the core's instanceDir does not exist, the directory is
created, but none of the JARs listed in solrconfig.xml in <lib> entries are
added to the classpath, thus resulting in ClassNotFound exceptions at runtime.
<lib> entries in solrconfig.xml are relative to core's instanceDir. It seems
that <lib> entries are processed before instanceDir is created and therefore
can't be resolved.
Example solr.xml:
<cores adminPath="/admin/cores" defaultCoreName="master1">
<core name="master1" instanceDir="master1" shard="shard1">
</core>
<core name="master2" instanceDir="master2" shard="shard2">
</core>
</cores>
solrconfig.xml:
...
<lib dir="../../dist" />
...
--
This message is automatically generated by JIRA.
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
