lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael McCandless <>
Subject Re: lucene and solr trunk
Date Tue, 16 Mar 2010 10:42:43 GMT
I think it like the 1st option best (lucene moves as subdir to solr's
current trunk SVN path), but I don't feel strongly.

This'd mean one could simply checkout lucene alone and do everything
you can do today.

But if you check out solr, you also get a full checkout of lucene, and
solr's build.xml will go and build lucene, copy over its jars to its
lib folder, and then do everything it currently does.

I think?

This small step is not much change over what we have today -- the code
simply moves, unchanged, except for some fixes to solr's build.xml to
go and build its lucene subdir first.

The bigger stuff, ideas on modules like renaming contrib->modules,
consolidating all analyzers, queries, queryparsers, highlighters, all
comes later.


On Mon, Mar 15, 2010 at 10:28 PM, Yonik Seeley <> wrote:
> Due to a tremendous amount of work by our newly merged committer
> corps, the get-on-lucene-trunk branch (branches/solr) is ready for
> prime-time as the new solr trunk!  Lucene and Solr need to move to a
> common trunk for a host of reasons, including single patches that can
> cover both, shared tags and branches, and shared test code w/o a test
> jar.
> The current Lucene trunk is: .../lucene/java/trunk
> The current Solr trunk is: .../lucene/solr/trunk
> So, we have a few options on where to put Solr's new trunk:
> Lucene moves to Solr's trunk:
>  /solr/trunk, /solr/trunk/lucene
> Solr moves to Lucene's trunk:
>  /java/trunk, /java/trunk/solr
> Both projects move to a new trunk:
>  /something/trunk/java, /something/trunk/solr
> -Yonik
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message