lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From NightOwl888 <>
Subject [GitHub] lucenenet issue #191: Migrating Lucene.Net to .NET Core
Date Tue, 22 Nov 2016 15:53:53 GMT
Github user NightOwl888 commented on the issue:
    Porting Highlighter is the plan, although to my knowledge nobody is currently working
on it. It has lagged behind primarily because it depends on the BreakIterator class, which
is part of the ICU functionality. Our current solution for this on the master branch (ICU4NET)
has issues running on some platforms, including .NET Core.
    On this branch @conniey has come up with another solution (icu-dotnet), which seems to
provide the same functionality, but has a different API than the original BreakIterator.
    So, I was hoping we could get this branch merged to master before porting it to avoid
some rework moving to the new API. That said, it wouldn't be a lot of rework.
    If you are willing to help out, I would suggest branching master and getting all of the
Highlighter tests to pass against ICU4NET - just look at Lucene.Net.Analysis.Th for an example
of its usage/installation. Submit a pull request targeting master. Then @conniey can simply
migrate them into this branch the same way she has been doing so far. There are ~50 files
to port including the tests, so I would estimate it would roughly take a couple of weekends
to complete. Interested?

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