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

Shawn Heisey commented on LUCENE-6722:
--------------------------------------

+1 to Uwe's idea.

My fuzzy recollections regarding the switch of trunk to Java 7 involve a 
*major* concerted effort around critical improvements in the language -- in 
particular, switching all file I/O to the new Files class.  I recall something 
about a big effort to switch to the diamond operator, and a smaller effort to 
use try-with-resources as well.  Those changes were extremely fundamental and 
very likely caused backporting hell, so I was not particularly surprised that 
we included those changes in branch_4x and jumped our Java requirement.

So far I have not seen any evidence that anyone is quite as keen to integrate 
new Java 8 features on a large scale.  If that changes, then trunk will deviate 
significantly from branch_5x, and when that happens, then we will have an 
extremely compelling reason to change the minimum Java version in 5x.

> 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