[ https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16799872#comment-16799872 ]
stack commented on HBASE-22052: ------------------------------- HBASE-22052-branch-2.1.003.addendum1.txt was empty. I messed it up. Retry with BASE-22052-branch-2.1.003.addendum2.txt. > 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 > Assignee: stack > Priority: Major > Fix For: 2.2.0, 2.0.5, 2.1.4 > > Attachments: HBASE-22052-branch-2.1.003.addendum2.txt, > HBASE-22052.2.1.003.addendum1.txt, HBASE-22052.branch-2.0.001.patch, > HBASE-22052.branch-2.0.002.patch, HBASE-22052.branch-2.0.002.patch, > HBASE-22052.branch-2.0.003.patch, HBASE-22052.branch-2.0.004.patch, > HBASE-22052.branch-2.1.001.patch, HBASE-22052.branch-2.1.002.patch, > HBASE-22052.branch-2.1.003.patch, HBASE-22052.branch-2.2.001.patch, > HBASE-22052.branch-2.2.002.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)