On Tue, Sep 15, 2009 at 7:31 PM, Chris Hostetter <hossman_luc...@fucit.org> wrote: > I remember a discussion about removing the /update/extract handler from > ./example/solr/conf/solrconfig.xml so that we could stop copying all the > jars into ./example/solr/lib/ and have a smaller, simpler, example.
I don't recall that... I did make the extract handler lazy such that one could easily remove all of the tika jars from the example w/o triggering an exception. We should look into updating the example README at a minimum. We should certainly strive for simplicity, but that can go either way... I like the "batteries included" mentality of python too. Future idea: - make "example" slightly more formal by naming it "server" - make server/solr/lib the home for some of these jars (preferably separated by sub-directory) and make compilation and tests go against these jars That would keep the "server" dir self contained (no outside references - copy it somewhere else to deploy), make our download smaller, and eliminate the copying around of libs. > The > idea being that then there would be a seperate distinct set of configs > providing an example of the extraction handler (with all of it's jars) If it's an example with all of it's jars, it seems like it's still a copy of all those jars, right? Or, we could put the example in contrib/extracting and make it such that the code and example server shared the libraries? -Yonik http://www.lucidimagination.com
