On Mar 8, 2014, at 11:17 AM, Uwe Schindler <[email protected]> wrote:
> [.] Move Lucene/Solr 4.8 (means branch_4x) to Java 7 and backport all Java > 7-related issues (FileChannel improvements, diamond operator,...). -0 -- Seems a little odd that we would force an upgrade on a minor version, which is not usually seen as best practice in development. A lot of users will have to completely re-certify their whole infrastructure when changing to a new JVM, which is a significant undertaking and thus I don't think this decision should be made casually. For instance, Dawid and I found a fairly nasty little bug where J6 swallows all exceptions in the thread completion service when the blocking queue is full, whereas J7 throws the exception. Some people might be in for a rude awakening on tracking that one down if they are using ThreadCompletionService. From what I see of our users in production, about 25% are on Java6 still, 75% are on either 7 or 8, with most of them being on 7. I think Typesafe had an interesting survey recently on Java version adoption, which might be worth examining as well. That being said, it's never easy to get people to go forward, so some times you just need to push them forward. > [.] Move Lucene/Solr trunk to Java 8 and allow closures in source code. This > would make some APIs much nicer. Our infrastructure mostly supports this, > only ECJ Javadoc linting is not yet possible, but forbidden-apis supports > Java 8 with all its crazy new stuff. +1. Better to do it before it is ever released and there is no time like the present. Heck, by the time 5 is released, J9 will probably be out and we can have this debate all over again! FWIW, this thread takes me back to the repeated debates on moving from JDK 1.4 to 1.5. What a horrible bikeshed that was. Go read the archives if you like. -Grant -------------------------------------------- Grant Ingersoll | @gsingers http://www.lucidworks.com
