[
https://issues.apache.org/jira/browse/HBASE-26717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484867#comment-17484867
]
Andrew Kyle Purtell commented on HBASE-26717:
---------------------------------------------
Thanks [~busbey]. I am pretty sure my build JDK was a very recent 8u. It is
possible I messed up the environment and it was 11u instead, I had both
versions installed into the VM, but not 17. I would not be surprised if there
are multiple paths to inclusion of the unrelocated bits. Regarding your advice:
bq. I think the right thing to do here is exclude these from the shading and
add a jdk specific profile to bring in the same compatibility dependencies.
I can take this up.
The first part is clear.
The second part... I assume you mean adding to the activation rule for JDK11+
these dependencies?
jakarta.xml.bind:jakarta.xml.bind-api
jakarta.activation:jakarta.activation-api
These jakarta dependencies appear in both reports so must be handled already
jakarta.ws.rs:jakarta.ws.rs-api
jakarta.annotation:jakarta.annotation-api
jakarta.validation:jakarta.validation-api
> [hbase-thirdparty] hbase-shaded-jersey packages unshaded classes
> ----------------------------------------------------------------
>
> Key: HBASE-26717
> URL: https://issues.apache.org/jira/browse/HBASE-26717
> Project: HBase
> Issue Type: Task
> Environment: Apache Maven 3.6.3
> Java version: 1.8.0_312, vendor: Andrew Purtell, runtime: /opt/java-8/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "5.10.0-11-arm64", arch: "aarch64", family: "unix"
> Reporter: Andrew Kyle Purtell
> Priority: Minor
>
> Found artifact with unexpected contents:
> '/home/apurtell/src/hbase/hbase-shaded/hbase-shaded-mapreduce/target/hbase-shaded-mapreduce-2.5.0-SNAPSHOT.jar'
> com/sun/activation/
> javax/activation/
> javax/xml/bind/
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
