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

Aleck Kulabukhov commented on SOLR-12809:
-----------------------------------------

I probably have an unpopular opinion here, but isn't better just to recommend 
*Java 8* for *Solr 6 and below* and *Java 8/11* for *Solr 7* and above? All the 
rest - on your own risk?

It's already a direction where everyone moves - either *8* or *11*.

Also it's a great idea to link to an external guide to outsource a burden of 
making a selection of Oracle/OpenJDK/whatever-else.

> Document recommended Java/Solr combinations (JDK 11?)
> -----------------------------------------------------
>
>                 Key: SOLR-12809
>                 URL: https://issues.apache.org/jira/browse/SOLR-12809
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Erick Erickson
>            Assignee: Erick Erickson
>            Priority: Major
>
> JDK 8 will be EOL early next year (except for "premier support"). JDK 9, 10 
> and 11 all have issues for Solr and Lucene IIUC.
> Also IIUC Oracle will start requiring commercial licenses for 11.
> This Jira is to discuss what we want to do going forward. Among the topics:
>  * Skip straight to 11, skipping 9 and 10? If so how to resolve current 
> issues?
>  * How much emphasis on OpenJDK .vs. Oracle's version
>  * What to do about dependencies that don't work (for whatever reason) with 
> the version of Java we go with?
>  * ???
> This may turn into an umbrella Jira with sub-tasks of course. Since JDK 11 
> has had a GA release, I'd also like to have a record of where the current 
> issues are to refer people to.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to