NihalJain commented on PR #131:
URL: https://github.com/apache/hbase-thirdparty/pull/131#issuecomment-2758017042

   > I am not sure about the name, but jetty12 wouldn't be great either.
   Yes hence thought to create env specific names.
   
   > I guess that importing two different relocated jetty versions is not 
something that we want support, so re-using the package name is fine
   
   Yes this is a fair concern. Although, we would not want to have shaded 
jetty9 in our classpath if with have jetty12-eeX, but I am afraid what if 
hadoop timeline service or something else brings it in indirectly.?


-- 
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]

Reply via email to