: 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
Ah.... ok, I missunderstood. : We should certainly strive for simplicity, but that can go either : way... I like the "batteries included" mentality of python too. agreed, but that goes back to that "have lots of examples, one really simple, many featuring differnet things, and one kitchen sink showing everything integrated together. BUt making that work without having a jar explosion requires lib refs which we haven't gotten arround to yet. : > 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? correct -- either way *we* have to make a copy of those jars somewhere in the release in order to demo Solr Cell. My point is that right now anyone who downloads a release, and makes a copy of "example/solr" to use as a set of starting configs (which is what we frequently advocate) winds up with a really *huge* solr home dir right off the bat because of all the extraction libs -- and extraction isn't exactly a "core" feature that everyon is going to want, so it doesn't really seem appropriate to provide it in the main example. If the main example was a kitchen sink example showing off *everything* and there was another "skeleton" exampel that would be fine ... but we've already gutted a bunch of cool stuff from example/solr in the interest of makining it "svelt" so this seems contradictory. -Hoss
