[
https://issues.apache.org/jira/browse/SOLR-17069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18036581#comment-18036581
]
ASF subversion and git services commented on SOLR-17069:
--------------------------------------------------------
Commit 641eaa420b7a4a7d668cf5fa40a0a998cc52bbed in solr's branch
refs/heads/branch_10x from David Smiley
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=641eaa420b7 ]
SOLR-17069 SOLR-17503: Don't include jetty-jakarta-servlet-api JAR (EE9) (#3838)
We should not have this JAR
org.eclipse.jetty.toolchain:jetty-jakarta-servlet-api as it is for Jakarta EE
9, and it contains javax XSD definitions. It also contains servlet classes for
v5 that compete with jakarta servlet-api v6 that we already depend on in some
places.
* Use mocking instead of implementing the entire HttpServletRequest and
response interfaces.
* toml: remove unused jetty lib references
* NOTICE: the servlet references were obsolete. The servlet JAR has it's own
license file, and isn't CDDL either.
(cherry picked from commit 50808cdcdb9c2985aff5995f9ff3f5c8782f1be0)
> 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
> Assignee: Sanjay Dutt
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 10.0
>
> Time Spent: 4h
> Remaining Estimate: 0h
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
