On Nov 24, 2008, at 3:16 PM, Grant Ingersoll wrote:
I was wondering what people thought of the following things that
have been bothering me, off and on, for a while.
1. Let's bring SolrJ into the core and have, as part of the release
packaging, a target that builds a standalone SolrJ jar for
distribution. Right now, we have circular dependencies between the
core and SolrJ such that I think it makes it painful to startup a
project in Eclipse or IntelliJ which thus makes it just that little
bit more difficult for new people to understand and contribute to
Solr. Besides, SolrJ is used by distributed search and is thus "core"
2. Likewise, let's refactor the appropriate servlet dependencies
such that it is in the core lib, but excluded from packaging, and
then utilized/copied out to the example where needed. I think
these are just the servlet apis used by the webapp part of the code.
The structure we had made some sense before solrj because a dependancy
on "core." Specifically I think we should have:
src/solrj (this will have common & client/src/solrj/*)
src/java (as is, but common would be moved to solrj)
src/servlet (moved from src/webapp/src)
I also think we could stand to simplify the example directory quite
a bit. Not quite sure what to do there just yet. While the
original "example" is still pretty easy to use, I think it's
confused by the proliferation (of which I am guilty) of other
"examples" that are thrown into the directory.
+1
I also think it would be nice to have a more timeless dataset for the
examples/tutorial. Using outdated computer hardware names is hard to
relate to :)
ryan
