lucene-dev mailing list archives

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


Grant Ingersoll commented on LUCENE-3151:

It's not too bad, except for the build system's recursive nature.  Not sure how to get around
that yet.

I did it for Token.  I think the others are useful at the definition layer if someone wants
just this piece of analysis, but not all of Lucene's implementations.  But, could be persuaded

QueryParserBase has a dep. here, so if we could fix that, then we might be able to do this.
  That being said, they are useful constructs for someone who wants them w/o all of Lucene's

I've got a new patch that helps here w/ some, but some of those utils are pretty useful in
the context of a common area, I guess.

> 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