[ 
https://issues.apache.org/jira/browse/LUCENE-6722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659658#comment-14659658
 ] 

Uwe Schindler commented on LUCENE-6722:
---------------------------------------

Hi,
we should not move the 5.x branch to Java 8 a this point. The differences 
between trunk and 5.x are not so big, so we can instead just switch to Lucene 6 
aka Trunk. Backporting all the Java 8 changes back to branch5x is a lot of 
work, because you have to pick lots of commits and backport them again.

I would like to prepare Lucene trunk to make it "releaseable" (e.g., fix the 
Stored/IndexDocument issues with docvalues) and then release 6.0 during the 
next year.

Most merge conflicts I see between trunk and 5.x are more related to 
Index/StorableDocument. The differences in Java code are minimal (we have some 
lambdas in trunk already, but nobody really did a "big rewrite" of that code). 
I backported some stuff that used Java 8 code in trunk, but that was quite 
simple.

So my vote:
-1 to move branch_5x to Java 8
+1 to work on releasing trunk as Lucene 6

> Java 8 as the minimum supported JVM version for branch_5x
> ---------------------------------------------------------
>
>                 Key: LUCENE-6722
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6722
>             Project: Lucene - Core
>          Issue Type: Wish
>            Reporter: Shalin Shekhar Mangar
>            Priority: Blocker
>             Fix For: 5.4
>
>
> Require Java 8 as the minimum supported JVM version for branch_5x.
> # Java 7 is already EOL'ed
> # Trunk is already at Java8
> # Important Solr components such as Jetty 9.3.x already require Java 8
> # Nashorn Javascript engine available in Java 8 is just so much faster and we 
> may see more usage of JS inside Solr (SOLR-7576 etc.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to