[
https://issues.apache.org/jira/browse/SOLR-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995103#comment-12995103
]
Hoss Man commented on SOLR-2364:
--------------------------------
This seems to have been caused by the following commits on Feb 11...
http://svn.apache.org/viewvc?view=revision&revision=1069656
http://svn.apache.org/viewvc?view=revision&revision=1069657
...which koji attributed to SOLR-1449, even though that issue (which added the
{{<lib/>}} feature was resolved back in 2009 and was included in Solr 1.4.1.
I really don't know why Koji did that ... as far as i'm concerned this is a
break in compatibility: the whole point of how these directives were setup was
to support the possibility of directories not existing. (and the examples
documented them as working that way)
Unless i here a strong reason to the contrary, i plan to revert those commits.
> <lib dir="..."/> directives are logging serious errors when they should not be
> ------------------------------------------------------------------------------
>
> Key: SOLR-2364
> URL: https://issues.apache.org/jira/browse/SOLR-2364
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Assignee: Hoss Man
> Fix For: 3.1, 4.0
>
>
> The {{<lib dir="foo" ... />}} syntax for solrconfig.xml was specificly
> designed so that it would *not* log errors if the directory (or jars in that
> directory) didn't exist -- this was designed to make it possible to have a
> {{<lib/>}} directive that would optionally include jars if they are not
> there, and ignore them if they can't be found ({{<lib
> path="foo/bar.jar".../>}} can be used when you have an explict jar you want
> to load and you want an error if it's not there)
> At some point in the not too distant past, something seems to have changed on
> both the 3x and trunk branches in how SolrResourceLoader.replaceClassLoader
> works, such that in the example you get errors logged like this...
> {noformat}
> Feb 15, 2011 4:52:03 PM org.apache.solr.core.SolrResourceLoader
> addToClassLoader
> SEVERE: Can't find (or read) file to add to classloader:
> /total/crap/dir/ignored
> {noformat}
> This is in spite of hte fact that the solrconfig.xml says...
> {noformat}
> <!-- If a dir option (with or without a regex) is used and nothing is found
> that matches, it will be ignored
> -->
> <lib dir="../../contrib/clustering/lib/downloads/" />
> <lib dir="../../contrib/clustering/lib/" />
> <lib dir="/total/crap/dir/ignored" />
> {noformat}
> Note these errors are also logged when running the example, even though there
> are no {{<lib/>}} declarations that corrispond to them -- they seem to be
> errors coming from the default behavior of looking for $solr_home/lib (which
> is evidently happening twice?)...
> {noformat}
> Feb 15, 2011 4:52:03 PM org.apache.solr.core.SolrResourceLoader <init>
> INFO: Solr home set to 'solr/'
> Feb 15, 2011 4:52:03 PM org.apache.solr.core.SolrResourceLoader
> addToClassLoader
> SEVERE: Can't find (or read) file to add to classloader: solr/./lib
> Feb 15, 2011 4:52:03 PM org.apache.solr.core.SolrResourceLoader <init>
> INFO: Solr home set to 'solr/./'
> Feb 15, 2011 4:52:03 PM org.apache.solr.core.SolrResourceLoader
> addToClassLoader
> SEVERE: Can't find (or read) file to add to classloader: solr/././lib
> {noformat}
--
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
