Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 4 Aug 2017 07:44:00 +0000 (UTC)
From: "Samir Ahmic (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13092393.1501832637000.91932.1501832640178@Atlassian.JIRA>
In-Reply-To: <JIRA.13092393.1501832637000@Atlassian.JIRA>
References: <JIRA.13092393.1501832637000@Atlassian.JIRA> <JIRA.13092393.1501832637677@jira-lw-us.apache.org>
Subject: [jira] [Created] (HBASE-18518) Remove jersey1* dependencies form
 project and jersey1* jars from lib dir
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 04 Aug 2017 07:44:06 -0000

Samir Ahmic created HBASE-18518:
-----------------------------------

             Summary: 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: 2.0.0-alpha-1, 3.0.0
            Reporter: Samir Ahmic
            Assignee: Samir Ahmic


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)