Details
-
Improvement
-
Status: Open
-
Blocker
-
Resolution: Unresolved
-
10.x
-
None
-
None
Description
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.
Attachments
Issue Links
- relates to
-
SOLR-17032 Jersey MessagingBinders class logs "A class javax.activation.DataSource for a default provider MessageBodyWriter<javax.activation.DataSource> was not found" warning on startup
- Open
-
SOLR-17069 Upgrade Jetty to 12.x
- Open
-
SOLR-15781 Make v2 APIs more REST-ful and migrate to JAX-RS
- Open
-
SOLR-16441 Upgrade Jetty to 11.x
- Open