[
https://issues.apache.org/jira/browse/SOLR-17503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18036234#comment-18036234
]
Gus Heck commented on SOLR-17503:
---------------------------------
Just for clarification in case the details of my prior comment are unclear or
have faded from memory:
* We do not need to remove javax package references where that javax is still
part of java SE (and thus still maintained and distributed by oracle)
* We do need to remove javax packages that were part of J2EE (the stuff that
moved to the Eclipse foundation)
So "javax" stuff is a slightly too broad of a phrase... all we need is to
remove the "J2EE javax" stuff
> 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: 0.5h
> 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]
