: Actually, I meant to say I have my Tokenizer jars in solr/lib.
: I have the jars that my Tokenizer jars depend in lib/ext,
: as I wanted them to be loaded only once per container
: due to their internal description. Bad idea?
unless there is something *really* hinky about those dependencies, i
9 4:28 PM
> To: solr-user@lucene.apache.org
> Subject: Right place to put my Tokenizer jars
>
> I have my custom Tokenizer and TokenizerFactory in a jar, and
> I've been putting it in example/lib/ext. and it's been
> working fine with Solr 1.3.
>
> This jar us
Hi Kurosaka-san,
I think you got a kind of class loader problem.
I usually put my plugin jars under the lib directory of solr home.
http://wiki.apache.org/solr/SolrPlugins#How_to_Load_Plugins
Koji
Teruhiko Kurosaka wrote:
> I have my custom Tokenizer and TokenizerFactory in a jar,
> and I've be
You're better off putting extensions like these in /lib and
letting Solr load them rather than putting them in a container
classpath like Jetty's lib/ext. As you've seen, conflicts occur
because of class loader visibility.
Erik
On Oct 14, 2009, at 7:28 PM, Teruhiko Kurosaka wrote:
I have my custom Tokenizer and TokenizerFactory in a jar,
and I've been putting it in example/lib/ext. and it's been
working fine with Solr 1.3.
This jar uses SLF4J as a logging API, and I had the SLF4J jars
in the same place, example/lib/ext.
Because Solr 1.4 uses SLF4J too and have it builtin,
