[ 
https://issues.apache.org/jira/browse/LUCENE-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044282#comment-13044282
 ] 

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


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


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: 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
>
>         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: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to