I fully agree with you yonik, it won't be a good idea to change to 1.5 within the patch releases of the version 2. But it is generally a good idea to think about using the 1.5 platform in future development. What's about using the 1.5 platform as a requirement on new projects like the contrib GDATA Server? We gonna have the same problem with the Gdata Server if we would go for Java 1.4 and the release of 1.6 is near, isn't it!
Simon On 5/27/06, Yonik Seeley <[EMAIL PROTECTED]> wrote:
On 5/27/06, Daniel Naber <[EMAIL PROTECTED]> wrote: > On Samstag 27 Mai 2006 18:11, Yonik Seeley wrote: > > > I understand legacy situations, but surely anyone doing a major Lucene > > upgrade can upgrade the JVM at the same time (the performance boosts > > alone are worth it.) > > You can get the improved performance by running 1.4 code with the 1.5 JVM, > right? So that shouldn't be a reason to require 1.5. My point was that most people doing a major upgrade of Lucene would also want to upgrade the JVM just for the performance boosts. Hence boosting the Lucene requirement to Java1.5 shouldn't be a burden for most people. However I don't think Lucene 2.0 is the right place for requiring Java5, since it's already released and has no Java1.5 requirement. If we changed now, we would be requiring a JVM upgrade for patch releases (not good). -Yonik http://incubator.apache.org/solr Solr, the open-source Lucene search server --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
