You should be able to compile your new plugin and use the <lib> directive in solrconfig.xml to point to your new jar. Solr should have access to all the lucene jar files at that point.
I usually build plugins after checking out all of the Solr source and doing an "ant dist" and pathing my IDE correctly. that way, the jar I produce doesn't have anything in it except my code and relies on Solr to resolve all the solr/lucene specific stuff... Best Erick On Thu, Jun 21, 2012 at 12:45 AM, Shameema Umer <shem...@gmail.com> wrote: > I am going to write a n update handler solr plugin. the original > DirectUpdateHandler2 imports mport org.apache.lucene.index and > org.apache.lucene.search. > But to add the lucene jar files into the classpath, I am not able to > find them in my solr package 3.4.0. Should i download lucene > separately to get the jar files? > > > Thanks > Shameema
