On Tue, Mar 16, 2010 at 2:31 PM, Michael McCandless < luc...@mikemccandless.com> wrote: > > If we move lucene under Solr's existing svn path, ie: > > /solr/trunk/lucene
Chiming in just a bit here - isn't there any concern that independent of whether or not people "can" build lucene without checking out solr, the mere fact that Lucene will be effectively a "subdirectory" of solr... is there no concern that there will then be a perception that Lucene is a subproject of Solr, instead of vice-versa? The way mavenified projects work is that there would instead be a top level in which both solr and lucene would be submodules (and thus also subdirectories in svn), with a dependency from solr to lucene (in the pom.xml for maven, but easy enough to do with the build.xml with ant). Checking out solr without lucene should be doable (using snapshot jars from lucene trunk nightly, maybe?), and the reverse should be easy, as could be checking out the top-level and getting everything (including a top-level build.xml which <include>'s or antcall's into the subdirectory build.xmls). It seems really weird to have Lucene appear as a subdirectory of Solr, especially for people out there who aren't using Solr. -jake
