[jira] [Resolved] (SOLR-17205) De-couple SolrJ required Java version from server Java version (main)

["Jan Høydahl (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-17205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Høydahl resolved SOLR-17205.
--------------------------------
    Fix Version/s: main (10.0)
       Resolution: Fixed

> De-couple SolrJ required Java version from server Java version (main)
> ---------------------------------------------------------------------
>
>                 Key: SOLR-17205
>                 URL: https://issues.apache.org/jira/browse/SOLR-17205
>             Project: Solr
>          Issue Type: Task
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrJ
>            Reporter: Jan Høydahl
>            Assignee: Jan Høydahl
>            Priority: Major
>             Fix For: main (10.0)
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Solr 9.x requires Java 11, both for server and solrj client.
> In Solr 10 we will likely bump required java version to Java 17, or maybe even 21, and since we are a standalone app we can do that - on the server-side.
> However, to give SolrJ client a broadest possible compatibility with customer application environments, we should consider de-coupling SolrJ's java requirement from the server-side. That would allow us to be progressive on the server side Java without forcing users to stay on latest Java in their apps.
> I don't know if it makes much sense to be compatible too far back on EOL java versions, but perhaps let SolrJ stay one LTS version behind the server for broad compatibility.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org