fsparv commented on PR #2876: URL: https://github.com/apache/solr/pull/2876#issuecomment-2518447174
> In my opinion, Jetty12 + EE8 is the best next step. > does it matter that this is ee10 vs ee8 like the description? https://issues.apache.org/jira/browse/SOLR-17503 (also linked from the ticket referenced above ticket). I don't have anything against continued support for javax per se, but there are definitely folks I've worked with that would benefit from being able to eliminate javax classes from their stack. Specifically they got tripped up by the appearance of jakarta based jetty versions (upgraded from other dependencies), which were then providing jakarta HttpServletRequests to tests based on our cloud solr test classes... boom. The goal with 17503 is to enable folks that integrate with our core code to use jakarta based servlet classes without explosion. If we do additional work to also continue to handle javax that's not a problem so long as Solr stops being the reason people can't upgrade their dependencies that also pull in jetty (or other jakarta based classes). One thing that's already sticky about our situation is our rest api stuff is already on jakarta packages ('jakarta.ws.rs:ja karta.ws.rs-api'). So IIUC, EE10 is simple to satisfy SOLR-17503 too, if we do more ok, but how important is that? is it worth the effort? I have a suspicion that we would involve separate artifacts and/or significant config gymnastics. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
