[jira] [Resolved] (HBASE-25908) Exclude jakarta.activation-api

["Michael Stack (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-25908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Stack resolved HBASE-25908.
-----------------------------------
    Fix Version/s: 2.5.0
                   3.0.0-alpha-1
     Hadoop Flags: Reviewed
             Tags: hadoop-3.3.1
       Resolution: Fixed

Merged to master and branch-2. Should I backport to branch-2.4 [~apurtell] ? You want to run on hadoop 3.3.1? Otherwise, hbase-2.5 to run on hadoop-3.3.1?

Thanks for the fix and the nice background [~weichiu].

> Exclude jakarta.activation-api
> ------------------------------
>
>                 Key: HBASE-25908
>                 URL: https://issues.apache.org/jira/browse/HBASE-25908
>             Project: HBase
>          Issue Type: Improvement
>          Components: hadoop3, shading
>    Affects Versions: 2.3.0
>            Reporter: Wei-Chiu Chuang
>            Assignee: Wei-Chiu Chuang
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.5.0
>
>
> Hadoop 3.3.1 replaced its dependency of javax.activation 1.2.0 with jakarta.activation 1.2.1.
> They are essentially the same thing (they even have the same classpath name), but Eclipse took over JavaEE development and therefore changed group/artifact id. (https://stackoverflow.com/questions/46493613/what-is-the-replacement-for-javax-activation-package-in-java-9)
> See HADOOP-17049 for more details. Hadoop 3.3.0 updated jackson-databind to 2.10 which shades jakarta.activation, causing classpath conflict.
> The solution to this issue will be similar to HBASE-22268



--
This message was sent by Atlassian Jira
(v8.3.4#803005)