This was actually something that we needed, if you looked at the commit dates, this is a few weeks old.
*Hibernating Rhinos Ltd * Oren Eini* l CEO l *Mobile: + 972-52-548-6969 Office: +972-4-622-7811 *l *Fax: +972-153-4-622-7811 On Fri, Mar 11, 2016 at 1:11 PM, Itamar Syn-Hershko <[email protected]> wrote: > Oren, Arkadiusz, Lucene.NET 3.x doesn't have any resemblance to the > Lucene.NET 4.8 code base. Same goes to most dependencies. It would have > been nice if this was contributed back to the project back in the day, but > now it doesn't help. > > -- > > Itamar Syn-Hershko > http://code972.com | @synhershko <https://twitter.com/synhershko> > Freelance Developer & Consultant > Lucene.NET committer and PMC member > > On Fri, Mar 11, 2016 at 7:53 AM, Arkadiusz Palinski <[email protected]> > wrote: > > > Also all of the dependencies of Lucene.NET are ported in the following > > branches: > > > > - https://github.com/ppekrol/PowerCollections/tree/master-dnx > > - https://github.com/ppekrol/GeoAPI/tree/master-dnx > > - https://github.com/ppekrol/NetTopologySuite/tree/master-dnx > > - https://github.com/ppekrol/Spatial4n/tree/master-dnx > > > > In order to compile Lucene.NET put all of the above in the same > directory. > > We had to change directory structure and project names, because CoreCLR > is > > taking project names (and dll names) from directory names. > > > > Some tests are intentionally skipped for CoreCLR, mostly because binary > > serialization is no longer supported there. > > > > > > On Fri, Mar 11, 2016 at 7:42 AM, Oren Eini (Ayende Rahien) < > > [email protected]> wrote: > > > > > We ported Lucene 3.0.3 (with some modifications that we needed) to > > CoreCLR, > > > you can find it here: > > > https://github.com/ppekrol/lucene.net/tree/3.0.3-dnx > > > > > > *Hibernating Rhinos Ltd * > > > > > > Oren Eini* l CEO l *Mobile: + 972-52-548-6969 > > > > > > Office: +972-4-622-7811 *l *Fax: +972-153-4-622-7811 > > > > > > > > > > > > On Fri, Mar 11, 2016 at 1:45 AM, Connie Yau <[email protected]> > > 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>, > > 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 > > > >." > > > > 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> > > > > 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 > > > > > > > > > > > > > > > -- > > Arek Palinski > > >
