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, 28 May 2011 20:11:47 GMT


Grant Ingersoll commented on LUCENE-3151:

I would propose to add:
lucene/src/analysis-defs that would contain all of the analysis declarations (including attributes)
and that the main build would depend on it being built first.  I thought about moving it to
modules/analysis, but that makes for some clunky Ant, IMO (although, I'm not sure if this
is less clunky.)

bq. but actually shove the analyzers-def into the lucene-core jar for simplicity/packaging
purposes if we want.
I'm not sure on shoving them into lucene-core just b/c I wonder if people might think they
need both jars then b/c they don't know if it's in core.  Not sure on that one, so I'm not
ruling it out.

> 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
> 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