[
https://issues.apache.org/jira/browse/LUCENE-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040668#comment-13040668
]
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: https://issues.apache.org/jira/browse/LUCENE-3151
> 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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
