[
https://issues.apache.org/jira/browse/LUCENE-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420147#comment-13420147
]
Uwe Schindler commented on LUCENE-3151:
---------------------------------------
How about using a tools to collect all realy needed dependencies from core and
package it as lucene-core4analysis-min.jar? JARJAR can do this (as ANT task,
without renaming classes, just to collect the dependent ones from core). We
would then also not need to remove the Javadocs (NRQ,...), Grant's patch
removed.
> 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-3151.patch, 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
