[ https://issues.apache.org/jira/browse/HBASE-18518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-18518: -------------------------- Fix Version/s: (was: 3.0.0) 2.0.0-alpha-3 > Remove jersey1* dependencies from 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 > Fix For: 2.0.0-alpha-3 > > Attachments: HBASE-18518-master-01.patch, HBASE-18518-master-02.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 (v6.4.14#64029)