Chris Hostetter wrote:
The bottom line is that contribs are about modularization, and
compartmentilization of features. We want to be able to build small
compact jars with well defined dependencies so that if someone wants
basic
indexing plus highlighting they know exactly what jars they need ...
they
don't have to worry about being surprized at run time by a
dependency on
some random class in o.a.l.misc, and they don't have to load every
Lucene jar (or one monolithic Lucene jar) just to play it safe.
I think it's very important to keep this modularization.
At the end of the day there's no reason not to think of the "core"
lucene
code base as anything other then a contrib which is not allowed to
have
dependencies, and needs to be Java 1.4 compatible. We could easily
imagine revamping the Lucene code base something like this...
mv contrib modules
mkdir modules/core
mv src/java modules/core/src
mv src/test modules/core/test
mv src/demo modules demo
...it would be a natural migration of what we have now (and it would
simplify the build process quite a bit).
+1
While it may seem at first like a simple directory reorganization, I
think this would be a powerful step forward in that "core" is side-by-
side with all other components in Lucene.
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
