[GitHub] [hbase] Apache9 commented on pull request #5210: HBASE-27820: HBase is not starting due to Jersey library conflicts wi…

2023-05-09 Thread via GitHub
Apache9 commented on PR #5210: URL: https://github.com/apache/hbase/pull/5210#issuecomment-1540328899 This is a known issue. I mean we could try to exclude these jars in hbase-assembly? -- This is an automated message from the Apache Git Service. To respond to the message, please log on

[GitHub] [hbase] Apache9 commented on pull request #5210: HBASE-27820: HBase is not starting due to Jersey library conflicts wi…

2023-05-05 Thread via GitHub
Apache9 commented on PR #5210: URL: https://github.com/apache/hbase/pull/5210#issuecomment-1535769913 The jars are required when running UTs, where we want to start mini MR cluster, IIRC. For me I do not think we need to ship these jars, as we do not want to start a mini MR cluster

[GitHub] [hbase] Apache9 commented on pull request #5210: HBASE-27820: HBase is not starting due to Jersey library conflicts wi…

2023-05-04 Thread via GitHub
Apache9 commented on PR #5210: URL: https://github.com/apache/hbase/pull/5210#issuecomment-1534517115 And we have shaded jersey in hbase-thirdparty and in hbase we should be using the shaded one, so could you please provide more information about the conflicts? What is the stack trace

[GitHub] [hbase] Apache9 commented on pull request #5210: HBASE-27820: HBase is not starting due to Jersey library conflicts wi…

2023-04-28 Thread via GitHub
Apache9 commented on PR #5210: URL: https://github.com/apache/hbase/pull/5210#issuecomment-1527577124 I think we should try to not ship this jar in the publish tarball, instead of excluding it when starting? -- This is an automated message from the Apache Git Service. To respond to the