From: Chris Hostetter <hoss...@fucit.org> To: solr...@lucene.apache.org Sent: Tue, March 16, 2010 6:46:19 PM Subject: Re: lucene and solr trunk

: Otis, yes, I think so, eventually. But that's gonna take much more discussion.

how modules : will be organized, yet... we'll get there, eventually.

direction that's distinct from the ultimate goal of better refactoring (especailly since that was one of the main goals of unifying development efforts)

simplicity: $svn = target=_blank >https://svn.apache.org/repos/asf/lucene)...

mv $svn/java/trunk $svn/java/tmp-migration svn mkdir $svn/java/trunk

svn mv $svn/java/tmp-migration $svn/java/trunk/core

point:

checking out $svn/java/trunk/core (i'm pretty sure existing checkouts will continue to work w/o any changes, the svn info should just update itself)

./core

can be modified to look at

care about Solr (including all committers) should start checking out and building all of $svn/java/trunk

all of $svn/java/trunk for releases ... AND/OR we could choose to branch specific modules (ie: solr) independently (with modifications to the build files on those branches to pull in their dependencies from alternate locations

of $svn/java/trunk/solr and $svn/java/trunk/core (like

$svn/java/trunk

"core" but don't care about certain "modules" (like solr) can do a simple non-recursive checkout of $svn/java/trunk and then do full checkouts of whatever modules

list things we *could* do if we go this route, i'm not advocating that we *should* do any of these things)

have raised to any of the previous suggestions which apply to this suggestion. Is there anything people can think of that would be useful, but not possible, if we go this route?