It occurred to me that we could also add a "core-example" target that
only builds the core example for those impatient types w/ slow
machines ;-)
On Dec 12, 2008, at 8:03 AM, Grant Ingersoll wrote:
On Dec 11, 2008, at 10:50 PM, Chris Hostetter wrote:
: Ignoring the JSP dilemma... DIH's JAR doesn't need to be in the
WAR, but can
: ship in a lib/ directory outside the WAR and come in as a
plugin. And Solr
: can ship with all of the contribs wired in to a kitchen-sink
example
: configuration.
:
: There is merit to keeping Solr's WAR and core to the most minimal
size
: possible and leveraging the plugin capability to let users reduce
the
: footprint and un-used parts.
+1 ... there really shouldn't be any contrib's in the war. If we're
worried that asking people to put the DIH jar in the plugin
directory is
too complicated for new users to understand (and i really can't
believe
that: if someone can understand ow to write a data-config.xml then
copying
a jar file should be trivial) we can make a "solr-kitchen-sink.war"
that
contains *every* contrib and *every* dependency in addition to the
regular
one.
But even that seems less useful in general then having a more
robust set
of examples -- where each one gets a lib directory populated with
just the
plugins it's demonstrating (and possibly a "kitchen-sink" example
showing
off all of them)
Honestly: I didn't even realize DIH was adding itself to the war
untill
recently, but then again i've been a little out of touch.
The only issue I see now is that DIH has been released as part of
the core, so I would vote that it stays in there. It is also quite
popular, I think, so I'd hate to break people.
