[
https://issues.apache.org/jira/browse/LUCENE-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418221#comment-13418221
]
Grant Ingersoll commented on LUCENE-3151:
-----------------------------------------
My goal is #1 (I have the same goal for the FST package). I want to be able to
use analyzers independently of Lucene and I don't want to have to bring in
whatever dependencies other parts of Lucene might have (which is admittedly
small at the moment). Doing this also achieves #2, I suppose. I've almost got
a patch ready that just makes this build sugar, but I wonder if it is better to
separate out the code if #1 is the goal.
> 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-ALPHA
> Reporter: Grant Ingersoll
> Fix For: 4.1
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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]
