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

ASF subversion and git services commented on SOLR-17503:
--------------------------------------------------------

Commit b001f39557df57d68cdc2403f31240ddb5c91a2b in solr's branch 
refs/heads/branch_10x from David Smiley
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=b001f39557d ]

SOLR-17503: Comple javax to Jakarta EE migration (#3839)

* smokeTestRelease needn't suppress its violation search of java/javax in JARs 
in certain places.
* forbidden-api; change javax.servlet->jakarta.servlet
* exclude javax.inject in tests of gcs-repository
* NOTICE.txt, remove obsolete references to servlet matters

(cherry picked from commit bc137a31d7cb67747c39e99fb6f4680d041167aa)


> Umbrella: Move to Jakarta J2EE packages
> ---------------------------------------
>
>                 Key: SOLR-17503
>                 URL: https://issues.apache.org/jira/browse/SOLR-17503
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 10.0
>            Reporter: Gus Heck
>            Assignee: David Smiley
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 10.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> In a recent migration from 8x to 9x I encountered a lot of issues where a 
> client with a repository containing custom solr components and fixes was 
> *still* unable to migrate to latest versions of critical packages like 
> dropwizard and hibernate validator because those packages rely on jakarta 
> packages, and even if it might be possible to re-arrange the decade plus old 
> repository and builds to avoid conflict the work to do so is prohibitive.
> Solr needs to not be the stick in the mud holding folks back. This ticket is 
> to collect/track tickets relating our dependency on the legacy javax classes.



--
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