Samir Ahmic commented on HBASE-18518:

Here is patch fixing issue with mixed jersey1 and jersey2 classes on REST 
project. After some digging i have find that we were using jersey1 classes only 
on few places in hbase code,  main source of jersey1 dependency is hadoop and 
can not be removed completely  since we are using it during testing in 
HBaseTestingUtility#startMiniDFSCluster() and similar functions which requires 
starting hadoop processes.
This patch also resolves https://issues.apache.org/jira/browse/HBASE-18506. And 
i will resolve it once we finish work here 

> Remove jersey1* dependencies form project and jersey1* jars from lib dir
> ------------------------------------------------------------------------
>                 Key: HBASE-18518
>                 URL: https://issues.apache.org/jira/browse/HBASE-18518
>             Project: HBase
>          Issue Type: Task
>          Components: dependencies, pom, REST
>    Affects Versions: 3.0.0, 2.0.0-alpha-1
>            Reporter: Samir Ahmic
>            Assignee: Samir Ahmic
>              Labels: cleanup
>         Attachments: HBASE-18518-master-01.patch
> Recently i have opened https://issues.apache.org/jira/browse/HBASE-18506 and 
> it is clear that is caused by mixing jersey1 and jersey2 jars in classpath. 
> With https://issues.apache.org/jira/browse/HBASE-12894 we have introduced 
> jersey2 to project,  and we also  have bunch of transitive dependencies 
> (mainly from hadoop) on jersey1 which is not happiest situation since jersey1 
> and jersey2 under same classpath can case runtime issues as it was case with 
> rest.
> This task will have following steps
> * Clean code and replace jersey1 constructs with jersey2 versions(there 
> should not be much of this)
> * Add exclusions for transitive jersey1 dependencies in pom.xml
> * Add exclusions  in hadoop-two-compat.xml to prevent jersey1 jars in lib dir

This message was sent by Atlassian JIRA

Reply via email to