[ https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16792907#comment-16792907 ]
stack commented on HBASE-22052: ------------------------------- 2.0.001 {code} M hbase-endpoint/pom.xml M hbase-http/pom.xml M hbase-mapreduce/pom.xml M hbase-rest/pom.xml M hbase-server/pom.xml M hbase-zookeeper/pom.xml Remove redundant version specification (and the odd property define done already up in parent pom). M hbase-it/pom.xml Explicitly reference hadoop-hdfs/hadoop-common just so we inherit exclusions; in particular the exclusion of jersey-core. Remove exclusion inherited from parent pom. M hbase-procedure/pom.xml Remove redundant version and classifier. M pom.xml Add jersey-core exclusions to all dependencies that pull it in. {code} > 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)