lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conniey <>
Subject [GitHub] lucenenet issue #203: API Work - Stabilization
Date Tue, 14 Feb 2017 05:04:49 GMT
Github user conniey commented on the issue:
    @NightOwl888 I apologise for the delayed response to your NUnit tests. I've been working
on another project. Is there anything I can help with?
    My current tasks for Lucene.NET that I would want to merge into this PR are:
    * Bring BreakIterator changes into local icu-dotnet .NET Core branch.
    * Use icu-dotnet's new way of loading NativeLibrary dependencies
       * There have been a lot of churn in the icu-dotnet repository since I created my issue
about migrating to .NET Core.  They changed the way that they ingested Native library dependencies
and split it into a different repository that I have to merge to and take into account.
    * Fix assembly loading changes in .NET Core
      * Recently, icu-dotnet introduced a new way of loading assemblies that uses native Windows/Linux
API calls rather than using a [DllImport] from C#.  Since we implemented a new way to load
native libraries in .NET Core (via /runtimes/{RID}/ rather than adding to the Environment.Path),
it breaks loading in .NET Core.  I need to research how to get the native library runtime
paths in .NET Core.  Then figure out how to load it first when they are using the Windows/Linux
    * Modify [](
to consumable rules for icu-dotnet

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