[Lucene.Net] [jira] Commented: (LUCENENET-380) Evaluate Sharpen as a port tool
[ https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998150#comment-12998150 ] Prescott Nasser commented on LUCENENET-380: --- I see this is assigned to me - but I'm hoping some other folks have been playing with sharpen? Also, at this point what are our other options? We could do something like tangible softwares java to C# - but that costs money and is likely not as extensible > 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
[Lucene.Net] [jira] Commented: (LUCENENET-380) Evaluate Sharpen as a port tool
[ https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998156#comment-12998156 ] Troy Howard commented on LUCENENET-380: --- So far Sharpen seems to be the most viable option. Worth noting: NGit (a .NET port of JGit) is also using Sharpen to do their code generation. They have pretty good documentation about the process. They have developed a bunch of support classes to enable the Sharpen conversion. I was thinking of contacting Lluis (developer of NGit), and seeing if he would be able to help us get our Sharpen setup rolling, or at least help evaluate our use case. Anyhow, check out the project at: https://github.com/slluis/ngit > 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
[Lucene.Net] [jira] Commented: (LUCENENET-380) Evaluate Sharpen as a port tool
[ https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998172#comment-12998172 ] Alex Thompson commented on LUCENENET-380: - Looks like NGit does the pre/post as patches. I think we can make the pre/post more integrated and generalized by extending sharpen. Their support classes do look useful. > 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
[Lucene.Net] [jira] Commented: (LUCENENET-380) Evaluate Sharpen as a port tool
[ https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998175#comment-12998175 ] Troy Howard commented on LUCENENET-380: --- Alex - I was thinking we could fork Sharpen along those lines. AFAIK, Sharpen doesn't accept contributions, and including the source code in our repo would require them to donate to us... So we'd have to do that outside of the ASF. We could bring together both changes to Sharpen to reduce pre/post patches and also create a reusable set of Support classes starting with the ones at NGit. Perhaps over time we could convince db4o to merge our fork back in, or donate Sharpen to ASF. > 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
[Lucene.Net] [jira] Commented: (LUCENENET-380) Evaluate Sharpen as a port tool
[ https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998181#comment-12998181 ] Alex Thompson commented on LUCENENET-380: - I saw db40 did accept a patch from an outside user, but it was a pretty small fix. For our more significant changes a fork is probably better so our progress is not dictated by 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: 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
[Lucene.Net] [jira] Commented: (LUCENENET-380) Evaluate Sharpen as a port tool
[ 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
[Lucene.Net] [jira] Commented: (LUCENENET-380) Evaluate Sharpen as a port tool
[ https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998186#comment-12998186 ] Prescott Nasser commented on LUCENENET-380: --- Sharcene, Larpen, LarceneLupen! > 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
[Lucene.Net] [jira] Commented: (LUCENENET-380) Evaluate Sharpen as a port tool
[ https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998220#comment-12998220 ] Troy Howard commented on LUCENENET-380: --- Regarding forking Sharpen, on second thought, they do seem to have activity on the project. The most recent commit was 2/21/2011, there is an issue tracker, a somewhat active Sharpen user forum, and have accepted outside patches in the not so distant past. Forking might not be appropriate unless it's just for the purposes of working on a complex patch. Perhaps we should contact the maintainers at db4o and let them know about our intended use of Sharpen, and see how they feel about getting regular patches from us. Maybe we can streamline the process a bit. > 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
[Lucene.Net] [jira] Commented: (LUCENENET-380) Evaluate Sharpen as a port tool
[ https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998626#comment-12998626 ] Alex Thompson commented on LUCENENET-380: - That's worth a shot I guess. Forum thread I started: http://developer.db4o.com/Forums/tabid/98/aft/10503/Default.aspx > 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
[Lucene.Net] [jira] [Commented] (LUCENENET-380) Evaluate Sharpen as a port tool
[ https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008965#comment-13008965 ] Prescott Nasser commented on LUCENENET-380: --- probably have to fork - we'll likely move very quickly at the start for changes. Once we stablize - maybe we can toss it back to them as a patch. We may find we are making changes that they won't accept > 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
[Lucene.Net] [jira] [Commented] (LUCENENET-380) Evaluate Sharpen as a port tool
[
https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009792#comment-13009792
]
Scott Lombard commented on LUCENENET-380:
-
I read the dOCL as one of three licensing options. From the dOCL:
{quote}You may obtain copies of the Software by download from the Versant
website. Software governed by this Agreement and Software governed by the GPL
are obtained from the same source. For this reason, portions of the Software
may be flagged as governed by the GPL license. However, the terms under which
Versant licenses the Software to you depend on your choice of license,
regardless of any GPL notices contained in the Software.{quote}
We are a FLOSS Application:
{quote}4. Free/Libre and Open Source Software Licenses
Where your FLOSS Application contains software components that were licensed
pursuant to one of the FLOSS licenses set forth below ("FLOSS Licenses"), you
may distribute such software components subject to that pre-existing FLOSS
License.
...
b. Apache Software License, versions 1.0, 1.1, or 2.0{quote}
I don't know if our fork will be Derived Software:
{quote}3. Derivative Works
For the purpose of this Agreement, software is deemed a derivative work of the
Software ("Derivative Work") where it is based on the Software, including
without limitation in the following circumstances:
a. the software is compiled against the Software;
b. the software contains specific references to the Software;
c. the software requires the Software to work; or
d. the software uses the proprietary API to the Software. {quote}
My concerns are more about the requirement to have a project link on the db4o
project website and who owns the changes to the sharpen.
To keep a GPL license we could not include it in the ASF repository. The GPL
license is acceptable for using the sharpen fork as build tool for Lucene.Net.
So the fork would become a separate project and I think would have to be
maintained independently of ASF.
What do other projects do?
> 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
[Lucene.Net] [jira] [Commented] (LUCENENET-380) Evaluate Sharpen as a port tool
[ https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009794#comment-13009794 ] Alex Thompson commented on LUCENENET-380: - Yes we already knew the fork would be outside ASF and not distributed with Lucene.Net so GPL will work. > 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
[Lucene.Net] [jira] [Commented] (LUCENENET-380) Evaluate Sharpen as a port tool
[ 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
[Lucene.Net] [jira] [Commented] (LUCENENET-380) Evaluate Sharpen as a port tool
[ https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010206#comment-13010206 ] Alex Thompson commented on LUCENENET-380: - My thoughts on the fork have been to make something that would be useful beyond Lucene, and the scope of the problems seem to be beyond the scope of Lucene.Net, so I do think an independent project would be a more natural fit. And if we used say BitBucket, would the infrastructure really be that much of a barrier? > 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
