On 03/04/2010 01:16 PM, Chris Hostetter wrote:
: In particular, how would the above baby step address the code
: duplication (my goal in the original opening) -- eg the 3 places where
: concrete analyzers/queries are today. How would it lead to making
: facets work with pure Lucene? To developing spatial in one place?
Having a shared dev list and a unified committer base should (in theory)
help improve the situation of duplicated functionality and promote
refactoring (ie: all commiters are on the same page, and can add/move
classes/tests arround)
If those changes don't have that effect, then i really don't see how
integrating the build processes or releases cycles will ever improve the
situation.
-Hoss
If Solr is not on Lucene trunk, that's not going to happen.
Solr on Lucene trunk is key. Release cycles is key to that.
Build process is key to getting devs that stick in one world to branch
into the other just a bit.
--
- Mark
http://www.lucidimagination.com
