lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From NightOwl888 <>
Subject [GitHub] lucenenet issue #188: Fixed 64 Failing Facet Tests and Finished Facet Implem...
Date Thu, 29 Sep 2016 13:48:14 GMT
Github user NightOwl888 commented on the issue:
    > which of the sub-project not ported yet?
    AFAIK, these are the pieces that are missing that are not currently being worked on, but
you should send an email to `` and ask for the all clear to prevent
any duplicate work (and if you don't receive a reply, consider it a "go ahead").
    AFAIK, No External Dependencies (may want to double check, though)
    QueryParser.Flexible (QueryParser has open pull requests...better to wait until they are
    With External Dependencies 
    Analysis.ICU (Depends on ICU4j)
    Analysis.Morfologik (Depends on Morfologik)
    Analysis.Phonetic (Depends on Apache Commons)
    Analysis.UIMA (Depends on Tagger, uimaj-core, WhiteSpaceTokenizer)
    Benchmark (many dependencies)
    Highlighter (Depends on Collator (which is still being ported) and BreakIterator (which
we don't have a good solution for yet))
    Sandbox (Depends on Apache Jakarta)
    The projects with external dependencies need some research to find out if there are any
good ports of those dependencies already out there. Even if they don't have, much of the code
doesn't depend on those external dependencies, so we can get a head start on it by porting
the parts that don't.
    It almost goes without saying, we need both the code and the tests ported so we can see
where the bugs are.
    Also, be sure you are looking at the [4.8.0 tag](
when porting over the code (its difficult enough to get the pieces to fit without having to
contend with different versions, too).

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message