lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shad Storhaug (JIRA)" <>
Subject [jira] [Commented] (LUCENENET-565) Port Lucene.Net.Replicator
Date Tue, 11 Jul 2017 09:46:00 GMT


Shad Storhaug commented on LUCENENET-565:

Good to hear.

Yea, I figured it would probably end up being a new project. I have been giving this some
thought, as we want to keep the Lucene-ported code physically separate from the ".NET Contrib"
code (which there will probably be more of after this). But I haven't yet worked out exactly
where to put it.

I look forward to reviewing your solution on a PR.

bq. And then there is the process of getting it onto .NET Standard 1.6.

Actually, we have been standardizing on .NET Standard 1.5. It isn't "the bigger the number
the better" in this case - Microsoft recommends using the lowest number you can. But just
for the simple fact that I have no idea what would happen if you have 50 DLLs that are on
a mixed bag of various versions of .NET Standard (nor does it seem to be documented how to
handle that particular can of worms), we should aim for .NET Standard 1.5 on all of them even
though some could potentially go lower, just because that is the lowest we can go on Lucene.Net

As for the conversion process - it is usually not very difficult. Copy and paste the {{project.json}},
{{<projectname>.project.json}} and {{<projectname>.xproj}} files from one of the
other projects (and its test project), edit the dependencies to match the {{.csproj}}, add
the project to the {{Lucene.Net.Portable.sln}} solution, then fix compile errors (sometimes
requires including a NuGet dependency or two).

Anyway, keep up the good work (y)

> Port Lucene.Net.Replicator
> --------------------------
>                 Key: LUCENENET-565
>                 URL:
>             Project: Lucene.Net
>          Issue Type: Task
>          Components: Lucene.Net.Replicator
>    Affects Versions: Lucene.Net 4.8.0
>            Reporter: Shad Storhaug
>            Priority: Minor
>              Labels: features

This message was sent by Atlassian JIRA

View raw message