lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Itamar Syn-Hershko <ita...@code972.com>
Subject Re: Moving Lucene.NET to .NET Core
Date Thu, 07 Apr 2016 19:41:22 GMT
Awesome work, thanks Elizabeth and team

I will look into your questions in more depth later - and will also try to
connect you with some potential beta testers. Also, our test harness should
be good enough to test it, and if it isn't in that areas - that would be
something that's worth improving.

Ok to require VS2015. Go for it.

Thanks again!

--

Itamar Syn-Hershko
http://code972.com | @synhershko <https://twitter.com/synhershko>
Freelance Developer & Consultant
Lucene.NET committer and PMC member

On Thu, Apr 7, 2016 at 3:28 PM, Elizabeth Maher (NEWMAN) <
Elizabeth.Maher@microsoft.com> wrote:

> Lucene.NET Community,
>
>
>
> After spending more time with this code base we have a better idea of the
> best way to approach migrating everything .NET core.
>
>
>
> There are two types of work.  The first is to removing/replacing external
> dependencies that do not work on .NET Core.  The second is only use classes
> on available on .NET Core  Here are the major work items we have identified.
>
> 1.       Remove use of SharpZipLib dependency – completed
>
> 2.       Update ICU4NET dependency for .NET Core – In Progress
>
> a.       PR almost ready for main branch
>
> 3.       Remove Appache.NMS dependency – Starting
>
> a.       PR will be created for main branch.
>
> b.       We believe this is the highest risk part of the migration
> process.  Connie has a separate thread going for this.  We, will of course
> make sure passing tests continue to pass.  We were hoping for a little help
> from the community on this one.  Would it be possible for a couple people
> to volunteer to try out this PR (when it is ready) on their own
> applications?
>
> 4.       Make portable libraries to build .NET Core binaries – In Progress
>
> a.       This work is being down at
> https://github.com/conniey/lucenenet/tree/move2dnx.  It looks like a
> large change, but it’s actually just added files to support the new project
> system and just a few minor changes to make sure code compiles on .NET
> Core.
>
> o   We will create a Lucene.Net.Portable.sln for build specifically for
> .NET Core.  We feel having two solutions will be the easiest transition for
> the community and the CI build system.
>
> o   This work will include porting tests.  We will verify that currently
> passing tests will continue to pass.
>
>
>
> We would also like to make sure this project is set up for success.  It’s
> awesome to see you already have a CI build process going.  We will continue
> to make sure the that build works and make sure the main Lucene.NET project
> builds with VS2013.  However, you will need VS2015 to compile the
> Lucene.NET.Portable solution.  Would it be possible to switch to using
> VS2015 or add another CI build for the portable solution?
>
>
>
> Hopefully that answers your questions.  Please let me know if you have
> further questions.
>
>
>
> Thanks,
>
> Elizabeth and Connie
>
>
>
> *From:* itamar.synhershko@gmail.com [mailto:itamar.synhershko@gmail.com] *On
> Behalf Of *Itamar Syn-Hershko
> *Sent:* Friday, March 11, 2016 3:10 AM
> *To:* dev@lucenenet.apache.org
> *Cc:* Elizabeth Maher (NEWMAN) <Elizabeth.Maher@microsoft.com>; Daniel
> Plaisted <daplaist@microsoft.com>; Bertrand Le Roy <beleroy@microsoft.com>
> *Subject:* Re: Moving Lucene.NET to .NET Core
>
>
>
> Hi Connie,
>
>
>
> That's great news, thanks!
>
>
>
> Please base your work on the master branch here:
> https://github.com/apache/lucenenet. We will fix the wording on the
> website, thanks for noticing.
>
>
>
> Building via Lucene.NET.sln should work - can you let us know if it
> doesn't?
>
>
>
> With regards to release dates and priorities - we currently don't have any
> ETA since development is currently going on very slowly. The plan was to
> finish fixing the last of the failing tests in Lucene.NET Core, complete
> porting the major subprojects (e.g. Analysis) with tests, and then approach
> compiling on .NET Core. Can you help us progress based on this roadmap, or
> are your resources limited to compiling on .NET Core?
>
>
>
> As for PRs - do you have an estimation of the amount / scope of changes
> required? is the result going to be another project or the same codebase
> compiling on .NET Core?
>
>
>
> Thanks again for joining us in this effort!
>
>
> --
>
>
>
> Itamar Syn-Hershko
>
> http://code972.com
> <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fcode972.com%2f&data=01%7c01%7cElizabeth.Maher%40microsoft.com%7c6804399b6f204e5da25208d3499da9fb%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=i9XhFfIuPyHjJap73M%2fmAazkbOnus4JjKRtKltTx4As%3d>
|
> @synhershko
> <https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2ftwitter.com%2fsynhershko&data=01%7c01%7cElizabeth.Maher%40microsoft.com%7c6804399b6f204e5da25208d3499da9fb%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=dco5pTxx02cLjH9mNI3ByFBogaSYsbV%2frotmOzZTT2k%3d>
>
> Freelance Developer & Consultant
>
> Lucene.NET committer and PMC member
>
>
>
> On Fri, Mar 11, 2016 at 12:45 AM, Connie Yau <conniey@microsoft.com>
> wrote:
>
> Hi all,
>
> Our team is working to make Lucene.NET run on .NET Core and was wondering
> if anyone else was working on this or would it be alright if we started
> this effort?
>
> Also, I was hoping that someone could answer a few questions I have about
> this project:
>
> 1.       What branch should we be basing our effort on?
>
> *         In Community<http://lucenenet.apache.org/community.html
> <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flucenenet.apache.org%2fcommunity.html&data=01%7c01%7cElizabeth.Maher%40microsoft.com%7c6804399b6f204e5da25208d3499da9fb%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=zLXh3HOEdMmXKOnnsMpH5n3lgti9F%2flvg%2b0rd8FztsI%3d>>,
> the documentation says "Most work currently happens on the branch named
> branch_4x<
> https://git-wip-us.apache.org/repos/asf?p=lucenenet.git;a=shortlog;h=refs/heads/branch_4x
> <https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgit-wip-us.apache.org%2frepos%2fasf%3fp%3dlucenenet.git%3ba%3dshortlog%3bh%3drefs%2fheads%2fbranch_4x&data=01%7c01%7cElizabeth.Maher%40microsoft.com%7c6804399b6f204e5da25208d3499da9fb%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=FQN5oT40VBc6DWU674apXS6Ue5jFr8%2b%2bpZRPo5tzfbg%3d>>."
> but it looks like the latest commits are in `master`
>
> 2.       How do we build this project?
>
> *         I read Build System & Scripts<
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=27824229
> <https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fcwiki.apache.org%2fconfluence%2fpages%2fviewpage.action%3fpageId%3d27824229&data=01%7c01%7cElizabeth.Maher%40microsoft.com%7c6804399b6f204e5da25208d3499da9fb%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=xBmwDkHtrrj21%2bVPkKPmTEVxPobXRuf6v0bDVEjhR1U%3d>>
> but there doesn't appear to be a build.cmd in the repository<
> https://github.com/apache/lucenenet>
>
> 3.       What is the expected release date for Lucene.NET v4.8?
>
> 4.       Regarding pull requests, is the preference for incremental
> changes (ie. Updating a set of APIs from one to another) or to have a large
> pull request (ie. Moving to run on .NET Core with all the associated
> project/code changes)?
>
> Thanks!
> Connie Yau
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message