[
https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998185#comment-12998185
]
Troy Howard commented on LUCENENET-380:
---------------------------------------
I guess the best thing to do is to put it to a 72 hour vote on the list.
It would cover, generally, using Sharpen for conversion, and by proxy creating
and maintaining a non-ASF fork of Sharpen that our process depends on.
The ultimate question, of course, is what should we call the fork? ;)
> 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: Prescott Nasser
> 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
