[
https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978816#action_12978816
]
Neal Granroth commented on LUCENENET-380:
-----------------------------------------
Thanks Alex,
What would be the plan for handling the Sharpen artifacts that prevent the
converted code from being built by the .NET SDK compiler?
Do you envision a post-conversion script to strip out statements like:
using Java.Lang
using Java.IO
and replace Sharpen-specific classes with standard .NET classes:
Sharpen.Collections.*
Sharpen.Runtime.*
> Evaluate Sharpen as a port tool
> -------------------------------
>
> Key: LUCENENET-380
> URL: https://issues.apache.org/jira/browse/LUCENENET-380
> Project: Lucene.Net
> Issue Type: Task
> Reporter: George Aroush
> 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.
-
You can reply to this email to add a comment to the issue online.
