: > assuming we have more use-case specific examples, wouldn't that just be
: > something that copies one of them to a target directory?
: 
: I guess what I really want is a way to be able to say:  Give me a Solr home
: that has these X features (DIH, Solr Cell, spell checking, highlighting, plus
: whatever libs are needed) with some basic configuration + my choice of a
: schema ranging from one that is barebones (maybe just an "id" field defined)
: to a "full fledged" one (the current example) and I want to be able to do it
: as simple as possible (i.e. as few commands as possible).

Ah.... i'm understanding now.  you don't just want a lot of good 
micro-examples of each feature, you want an easy way to generate "default" 
configs that work for an arbitrary set of features specified by the user.

That seems like a hard problem to get right in a generic way.

The simplest method i can think of for achiving that would be to start 
with a kitchen-sink type example that includes *everything* (because then 
it's easy to test that all of the pieces work well together and don't 
collide -- duplicate fieldnames or hanler names etc...) and then use xml 
comments or some other templating to be able to split that kitchen sink 
file up into snippets -- which could then be combined again in lots of 
combinations.

(Or ... I suppose the snippets could be maintained by hand and then the 
build system could generate the kitchen sink and run tests to ensure that 
none of them collide ... but maintaining the kitchen-sink by hand seems 
easier in a weird way)


-Hoss

Reply via email to