You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2019/03/14 17:42:00 UTC

[jira] [Updated] (HBASE-22052) pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications

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

stack updated HBASE-22052:
--------------------------
    Attachment: HBASE-22052.branch-2.0.001.patch

> pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-22052
>                 URL: https://issues.apache.org/jira/browse/HBASE-22052
>             Project: HBase
>          Issue Type: Task
>            Reporter: stack
>            Priority: Major
>         Attachments: HBASE-22052.branch-2.0.001.patch
>
>
> Working on HBASE-22029, where we fail compile of hbase-it module four hours into an RC build, it looks like transitive include of jersey-core is the culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue is about having hadoop2 profile and hadoop3 profiles match around jersey-core treatment. Some miscellaneous cleanups are also done.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)