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

Bernd Wahlen edited comment on SOLR-16441 at 3/31/23 3:04 PM:
--------------------------------------------------------------

- spring boot 2.7.y uses jetty 9.4
- spring boot 3 uses jetty 11
current solrj-9.2 uses jetty 10 client that is incompatible with both

working with solr in spring boot is very difucult now after solr is removed 
from spring data and now using solrj is also painful.
https://spring.io/blog/2020/04/07/spring-data-for-apache-solr-discontinued

i think solrj dependencies are manageable (most of the mentioned problems are 
not related to solrj). Can we just upgrade solrj (e.g. under different package 
solrj-jetty11 or something).
Most project include only the client library and will be happy with that. 


was (Author: bwahlen):
- spring boot 2.7.y uses jetty 9.4
- spring boot 3 uses jetty 11
current solrj-9.2 uses jetty 10 client that is incompatible with both

working with solr in spring boot is very difucult now after solr is removed 
from spring data and now using solrj is also painful.
https://spring.io/blog/2020/04/07/spring-data-for-apache-solr-discontinued

> Upgrade Jetty to 11.x
> ---------------------
>
>                 Key: SOLR-16441
>                 URL: https://issues.apache.org/jira/browse/SOLR-16441
>             Project: Solr
>          Issue Type: Improvement
>          Components: Server
>            Reporter: Tomas Eduardo Fernandez Lobbe
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Solr is currently using Jetty 9.4.x and upgrading to Jetty 10.x in 
> SOLR-15955, we should look at upgrade to Jetty 11 which moves from javax to 
> jakarta namespace for servlet.
>  



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

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

Reply via email to