lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shad Storhaug (Jira)" <>
Subject [jira] [Resolved] (LUCENENET-623) Port Lucene.Net.Analysis.OpenNLP
Date Sat, 26 Oct 2019 19:15:00 GMT


Shad Storhaug resolved LUCENENET-623.
    Fix Version/s: Lucene.Net 4.8.0
       Resolution: Fixed

Went with

even though it is an IKVM version, meaning no .NET Standard support. However, there are a
few people working on making IKVM function with .NET Standard 2.0, so this might be a viable
option down the road.

> Port Lucene.Net.Analysis.OpenNLP
> --------------------------------
>                 Key: LUCENENET-623
>                 URL:
>             Project: Lucene.Net
>          Issue Type: Task
>          Components: Lucene.Net.Analysis.UIMA
>            Reporter: Shad Storhaug
>            Assignee: Shad Storhaug
>            Priority: Minor
>              Labels: features
>             Fix For: Lucene.Net 4.8.0
>   Original Estimate: 40h
>  Remaining Estimate: 40h
> In Lucene 8.x, the Analysis.UIMA component has been replaced with Analysis.OpenNLP.
> This is good news for us, because there are at least a couple OpenNLP options in .NET,
a native port, and one using IKVM. Unfortunately, Lucene 8.x uses version 1.9.1 of OpenNLP,
for which there is no equivalent so compatibility must be checked. Perhaps the best option
would be to upgrade the first one (pull request) so we have native C# support, although the
fastest option would certainly to use the IKVM version (which has no .NET Standard support).
> This could make a great learning experience for how to port Java code to .NET, since
the OpenNLP package is quite small in size.

This message was sent by Atlassian Jira

View raw message