[ https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010051#comment-13010051 ]
Scott Lombard commented on LUCENENET-380: ----------------------------------------- Why fork outside of ASF if we can keep it inside? Is a independent project justified? It seems to me there is a lot of infrastructure that needs to be duplicated and maintained. I agreed to starting a fork outside of ASF because I didn't think there was any possibility to bring code into lucene.net. Now, I just don't understand licensing well enough to rule out a dOCL license from db4o. > Evaluate Sharpen as a port tool > ------------------------------- > > Key: LUCENENET-380 > URL: https://issues.apache.org/jira/browse/LUCENENET-380 > Project: Lucene.Net > Issue Type: Task > Components: Build Automation, Lucene.Net Contrib, Lucene.Net Core, > Lucene.Net Demo, Lucene.Net Test > Reporter: George Aroush > Assignee: Alex Thompson > Attachments: 3.0.2_JavaToCSharpConverter_AfterPostProcessing.zip, > 3.0.2_JavaToCSharpConverter_NoPostProcessing.zip, IndexWriter.java, > Lucene.Net.3_0_3_Sharpen20110106.zip, Lucene.Net.Sharpen20101104.zip, > Lucene.Net.Sharpen20101114.zip, NIOFSDirectory.java, QueryParser.java, > TestBufferedIndexInput.java, TestDateFilter.java > > > This task is to evaluate Sharpen as a port tool for Lucene.Net. > The files to be evaluated are attached. We need to run those files (which > are off Java Lucene 2.9.2) against Sharpen and compare the result against > JLCA result. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira