Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Date: Sat, 27 May 2006 11:51:50 -0700 (PDT)
From: Chris Hostetter <hossman_lucene@fucit.org>
To: java-dev@lucene.apache.org
Subject: Re: Lucene and Java 1.5
In-Reply-To: <200605271545.09231@danielnaber.de>
Message-ID: <Pine.LNX.4.58.0605271143140.13906@hal.rescomp.berkeley.edu>
References: <1148720927.5049.47.camel@localhost>
 <f18c9dde0605270347q34c98b10p16376c4a5c7b0b99@mail.gmail.com>
 <44783572.20108@manawiz.com> <200605271545.09231@danielnaber.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


: Java 1.5 has nice features, sure. But these features are mostly useful
: during development, they are less usefull for existing and proven software
: like Lucene. I think at least the core of Lucene should stay compatible

As I understood it, the long term road map has been that 2.0.* would be th
last major stable revision without serious API changes, and that 2.1.*
versions are where serious refactoring/API changes might take place.  Some
of those 1.5 features might be very handy durring that process, and the
use of Generics could help make the resulting APIs more self documenting
and bulletproof.

It seems to me that targetting 1.5 for 2.1.* is a smart way to proceed.


-Hoss


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org