[
https://issues.apache.org/jira/browse/SOLR-17503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18035672#comment-18035672
]
David Smiley commented on SOLR-17503:
-------------------------------------
What matters most is that we do not ship JARs with "javax" packages in them. I
posted [an additional PR|https://github.com/apache/solr/pull/3838] to the Jetty
migration JIRA that removes the last JAR.
Yes we should also cleanup/migrate some mere references to them.
> 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: 20m
> 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]
