[
https://issues.apache.org/jira/browse/HBASE-30452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18124593#comment-18124593
]
mazhengxuan commented on HBASE-30452:
-------------------------------------
I'd like to work on this issue. I confirmed that the 2.6.7 shaded testing util
contains unrelocated JUnit classes that are absent from 2.6.6. I plan to
exclude JUnit and its support libraries from the shaded jar, then add a
jar-content check and verify it with an external JUnit classpath.
> hbase-shaded-testing-util 2.6.7 bundles unshaded junit jars
> -----------------------------------------------------------
>
> Key: HBASE-30452
> URL: https://issues.apache.org/jira/browse/HBASE-30452
> Project: HBase
> Issue Type: Task
> Reporter: PJ Fanning
> Priority: Major
>
> 2.6.6 did not have unshaded junit classes - caused Apache Pekko build to fail
> because we use latest Junit Jupiter 6.0 jars and they conflict with the junit
> classes in hbase-shaded-testing-util
> The 2.6.7 packages:
> **JUnit 4**
> - `org.junit` (1 class: `Assert`)
> **JUnit Jupiter API**
> - `org.junit.jupiter.api` (93)
> - `org.junit.jupiter.api.condition` (38)
> - `org.junit.jupiter.api.extension` (51)
> - `org.junit.jupiter.api.extension.support` (1)
> - `org.junit.jupiter.api.function` (3)
> - `org.junit.jupiter.api.io` (4)
> - `org.junit.jupiter.api.parallel` (10)
> **JUnit Jupiter Engine**
> - `org.junit.jupiter.engine` (2)
> - `org.junit.jupiter.engine.config` (5)
> - `org.junit.jupiter.engine.descriptor` (56)
> - `org.junit.jupiter.engine.discovery` (17)
> - `org.junit.jupiter.engine.discovery.predicates` (6)
> - `org.junit.jupiter.engine.execution` (27)
> - `org.junit.jupiter.engine.extension` (45)
> - `org.junit.jupiter.engine.support` (2)
> **JUnit Jupiter Params**
> - `org.junit.jupiter.params` (58)
> - `org.junit.jupiter.params.aggregator` (8)
> - `org.junit.jupiter.params.converter` (10)
> - `org.junit.jupiter.params.provider` (40)
> - `org.junit.jupiter.params.support` (7)
> - `org.junit.jupiter.params.shadow.com.univocity.parsers.*` (273, across 15
> subpackages)
> **JUnit Platform Commons**
> - `org.junit.platform.commons` (2)
> - `org.junit.platform.commons.annotation` (1)
> - `org.junit.platform.commons.function` (5)
> - `org.junit.platform.commons.logging` (4)
> - `org.junit.platform.commons.support` (8)
> - `org.junit.platform.commons.support.conversion` (13)
> - `org.junit.platform.commons.support.scanning` (8)
> - `org.junit.platform.commons.util` (37)
> - Java 9+ copies under `META-INF/versions/9/org/junit/platform/commons/util/`
> **JUnit Platform Engine**
> - `org.junit.platform.engine` (33)
> - `org.junit.platform.engine.discovery` (40)
> - `org.junit.platform.engine.reporting` (3)
> - `org.junit.platform.engine.support.config` (1)
> - `org.junit.platform.engine.support.descriptor` (13)
> - `org.junit.platform.engine.support.discovery` (17)
> - `org.junit.platform.engine.support.filter` (1)
> - `org.junit.platform.engine.support.hierarchical` (51)
> - `org.junit.platform.engine.support.store` (10)
> Why the test failed: the jar has no org.junit.platform.launcher classes. On
> the HBase test classpath it comes before all the real JUnit jars. So our
> junit-platform-launcher 6.0.3 was paired with the old
> org.junit.platform.engine classes from inside this jar.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
