What is the proper way to deploy Solr with a custom schema.xml that requires extra JARs?

2010-01-12 Thread Teruhiko Kurosaka
I have schema.xml that uses a Tokenizer that I wrote.

I understand the standard way of deploying Solr is
to place solr.war in webapps directory, have a separate
directory that has conf files under its conf subdirectory,
and specify that directory as Solr home dir via either 
JVM property or JNDI.

I can't put the extra JARs in the Solr home dir's lib subdir,
can I?

Is there any elegant way of placing the extra JARs
other than expanding the war in webapp directory manually
and adding the JARs?

-kuro


Re: What is the proper way to deploy Solr with a custom schema.xml that requires extra JARs?

2010-01-12 Thread Otis Gospodnetic
 I can't put the extra JARs in the Solr home dir's lib subdir, can I?

Why, this is indeed what you should do, Kuro.

Otis
--
Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch



- Original Message 
 From: Teruhiko Kurosaka k...@basistech.com
 To: solr-user@lucene.apache.org solr-user@lucene.apache.org
 Sent: Tue, January 12, 2010 1:23:37 PM
 Subject: What is the proper way to deploy Solr with a custom  schema.xml that 
 requires extra JARs?
 
 I have schema.xml that uses a Tokenizer that I wrote.
 
 I understand the standard way of deploying Solr is
 to place solr.war in webapps directory, have a separate
 directory that has conf files under its conf subdirectory,
 and specify that directory as Solr home dir via either 
 JVM property or JNDI.
 
 I can't put the extra JARs in the Solr home dir's lib subdir,
 can I?
 
 Is there any elegant way of placing the extra JARs
 other than expanding the war in webapp directory manually
 and adding the JARs?
 
 -kuro