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

Gus Heck edited comment on SOLR-17069 at 8/14/24 2:45 PM:
----------------------------------------------------------

Why would we want to stick with javax? Edit: Reading back into the jetty 11 
issue. I see the dep issue, but the world is moving to Jakarta, we should 
too... also s3Mock now is jakarta packages because they wanted to support 
springboot: [https://github.com/adobe/S3Mock/releases/tag/3.10.0] see 
[https://github.com/adobe/S3Mock/commit/e8a5be905b47b9e7a3938fdf56c1a307aaff91f1]


was (Author: gus_heck):
Why would we want to stick with javax?

> Upgrade Jetty to 12.x
> ---------------------
>
>                 Key: SOLR-17069
>                 URL: https://issues.apache.org/jira/browse/SOLR-17069
>             Project: Solr
>          Issue Type: Improvement
>          Components: Server
>            Reporter: Kevin Risden
>            Priority: Major
>
> On SOLR-16441 PR it was mentioned that Jetty 12.x supports multiple servlet 
> versions and we could stick with javax.servlet instead of all the changes 
> required to go to Jetty 11.x in SOLR-16441 PR. 
> Jetty 12 requires JDK 17
> References:
> * https://webtide.com/introducing-jetty-12/
> * 
> https://eclipse.dev/jetty/documentation/jetty-12/programming-guide/index.html#pg-migration-11-to-12



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

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

Reply via email to