+1 and thanks for cleaning this up Uwe. the MR-JAR can be a good solution to use newer methods where available in specific cases, but it does not solve everything. We should allow opportunities in master branch such as potentially restructuring code to take advantage of the new module system and so on, which could drastically improve usability.
On Tue, Mar 19, 2019 at 5:01 PM Uwe Schindler <[email protected]> wrote: > > +1, let's do it. > > I can take care of commenting out the MR-JAR parts and migrating from > lucene.Future* to java.util.* (but we should not remove it from build files, > so we can use MR-JARS in the same way in future). > > Just open an issue once the vote has passed, I'l take care of removing the > Future* classes. > > Uwe > > ----- > Uwe Schindler > Achterdiek 19, D-28357 Bremen > http://www.thetaphi.de > eMail: [email protected] > > > -----Original Message----- > > From: Adrien Grand <[email protected]> > > Sent: Tuesday, March 19, 2019 7:23 PM > > To: Lucene Dev <[email protected]> > > Subject: [VOTE] Master/9.0 to require Java 11 > > > > Hello, > > > > Now that Lucene/Solr 8.0 has shipped I'd like us to consider requiring > > Java 11 for 9.0, currently the master branch. We had 18 months between > > 7.0 and 8.0, so if we assume a similar interval between 8.0 and 9.0 > > that would mean releasing 9.0 about 2 years after Java 11, which > > sounds like a conservative requirement to me. > > > > What do you think? > > > > Here is my +1. > > > > -- > > Adrien > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
