Return-Path: 
 <lucene-net-dev-return-5245-apmail-lucene-lucene-net-dev-archive=lucene.apache.org@lucene.apache.org>
X-Original-To: apmail-lucene-lucene-net-dev-archive@www.apache.org
Delivered-To: apmail-lucene-lucene-net-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id DA5F54DE9
	for <apmail-lucene-lucene-net-dev-archive@www.apache.org>;
 Wed, 29 Jun 2011 21:35:52 +0000 (UTC)
Received: (qmail 19001 invoked by uid 500); 29 Jun 2011 21:35:52 -0000
Delivered-To: apmail-lucene-lucene-net-dev-archive@lucene.apache.org
Received: (qmail 18912 invoked by uid 500); 29 Jun 2011 21:35:51 -0000
Mailing-List: contact lucene-net-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:lucene-net-dev-help@lucene.apache.org>
List-Unsubscribe: <mailto:lucene-net-dev-unsubscribe@lucene.apache.org>
List-Post: <mailto:lucene-net-dev@lucene.apache.org>
List-Id: <lucene-net-dev.lucene.apache.org>
Reply-To: lucene-net-dev@lucene.apache.org
Delivered-To: mailing list lucene-net-dev@lucene.apache.org
Received: (qmail 18631 invoked by uid 99); 29 Jun 2011 21:35:51 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jun 2011 21:35:51 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of digydigy@gmail.com designates
 209.85.161.53 as permitted sender)
Received: from [209.85.161.53] (HELO mail-fx0-f53.google.com) (209.85.161.53)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jun 2011 21:35:45 +0000
Received: by fxd23 with SMTP id 23so1180988fxd.12
        for <multiple recipients>; Wed, 29 Jun 2011 14:35:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=from:to:references:in-reply-to:subject:date:message-id:mime-version
         :content-type:content-transfer-encoding:x-mailer:thread-index
         :content-language;
        bh=EOITuvKoXI4mV0OtKAcMWIrosbJPWsqBFAXxIjJ85/Y=;
        b=iU1eLNK5yEG4Lr9Ga1iHLZGsAx+PFvvfFzsZ2WSiOpr3n2KNkaalIpHBNW6GIY956G
         ZuOpHf4BFIYhgGX4rUYxOFD90ZCn/TW8t4p6Sdof/iQVWmPR38qCfhe15l5ZN54XM7fz
         24L5gbqRr86ZVl9RXpkNJlRLQ9GUKjffKPwU0=
Received: by 10.223.132.210 with SMTP id c18mr1858599fat.97.1309383323910;
        Wed, 29 Jun 2011 14:35:23 -0700 (PDT)
Received: from NEWPC ([81.213.206.230])
        by mx.google.com with ESMTPS id b13sm1142874fab.36.2011.06.29.14.35.22
        (version=SSLv3 cipher=OTHER);
        Wed, 29 Jun 2011 14:35:23 -0700 (PDT)
From: "Digy" <digydigy@gmail.com>
To: <lucene-net-dev@lucene.apache.org>,
	<lucene-net-user@lucene.apache.org>
References: <7B6EFA02C5D14F93A2F7AA03F9D04031@kingindustries.local>
In-Reply-To: <7B6EFA02C5D14F93A2F7AA03F9D04031@kingindustries.local>
Date: Thu, 30 Jun 2011 00:34:58 +0300
Message-ID: <000001cc36a4$65f51a00$31df4e00$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acw2jm2JhERdfdhVQvWjo0t4ClohKwAE/2DQ
Content-Language: tr
Subject: RE: [Lucene.Net] Is a Lucene.Net Line-by-Line Jave port needed?

Hi Scott,
Please avoid crossposting(as I do now). Since when I reply to your eMail, it
goes to one of the lists and thread is splitted into two.
It may be good for announcements but not for discussions.

DIGY

-----Original Message-----
From: Scott Lombard [mailto:lombardenator@gmail.com] 
Sent: Wednesday, June 29, 2011 9:58 PM
To: lucene-net-dev@lucene.apache.org; lucene-net-user@lucene.apache.org
Subject: [Lucene.Net] Is a Lucene.Net Line-by-Line Jave port needed?

 

After the large community response about moving the code base from .Net 2.0
to Net 4.0 I am trying to figure out what is the need for a line-by-line
port.  Starting with Digy's excellent work on the conversion to generics a
priority of the 2.9.4g release is the 2 packages would not be
interchangeable.  So faster turnaround from a java release won't matter to
non line-by-line users they will have to wait until the updates are made to
the non line-by-line code base.  

 

My question is there really a user base for the line-by-line port?  Anyone
have a comment?

 

Scott