NihalJain commented on PR #131: URL: https://github.com/apache/hbase-thirdparty/pull/131#issuecomment-2758060663
> IUC since the eeX stuff is in separate packages, we could add any or all ee specification modules. > If we keep the ee8 name, then migrate to ee9/10 for jakarta, then the module/artifact name will be misleading. > I would rather add the additional eeX modules to existing jetty thirdparty tha duplicate everything for each one. Exactly that is the plan. Please refer https://issues.apache.org/jira/browse/HBASE-29224 > Phase 2: Add Jetty 12 with EE9 to hbase-thirdparty and jersey 3. And may be some other artifacts (not sure at this point) Next consume this version of hbase-thirdparty, move to jetty 12 with EE9, bump jakarta servlet to 5.x / 6.x, tomcat to 10.x / 11.x and migrate all the dependencies and code to jakarta namespace Blockers?? Hadoop AuthenticationFilter dependent and related code need to be either shaded to move from javax to jakarta, or we would need to wait for hadoop for move to jakarta. (In my rough analysis, I have identified this till now, when we attempt it might be more stuff) Test and verify everything is working as expected. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
