lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grant Ingersoll (JIRA)" <>
Subject [jira] [Updated] (LUCENE-3151) Make all of Analysis completely independent from Lucene Core
Date Sat, 28 May 2011 22:54:47 GMT


Grant Ingersoll updated LUCENE-3151:

    Attachment: LUCENE-3151.patch

doesn't fully compile yet (but core does) due to our recursive build system, but at least
fleshes out the proposed directory layout.  I may, however, change src/declarations to src/common
and then we would have lucene-common.jar.  I was surprised by how much I needed to move out
of core (e.g. BytesRef)

> Make all of Analysis completely independent from Lucene Core
> ------------------------------------------------------------
>                 Key: LUCENE-3151
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>    Affects Versions: 4.0
>            Reporter: Grant Ingersoll
>             Fix For: 4.0
>         Attachments: LUCENE-3151.patch
> Lucene's analysis package, including the definitions of Attribute, TokenStream, etc.
are quite useful outside of Lucene (for instance, Mahout uses them) for text processing. 
I'd like to move the definitions, or at least their packaging, to a separate JAR file so that
one can consume them w/o needing Lucene core.  My draft idea is to have a definition area
that Lucene core is dependent on and the rest of the analysis package can then be dependent
on the definition area.  (I'm open to other ideas as well)

This message is automatically generated by JIRA.
For more information on JIRA, see:

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

View raw message