[
https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16799405#comment-16799405
]
stack commented on HBASE-22052:
-------------------------------
I'd opened subissue HBASE-22088 to figure 'publishHTML gone mad' but it looks
like publishHTML is fine. The fail is elsewhere in a shaded mapreduce client IT
test that won't timeout. See tail of HBASE-22088 for extract from build log
(found by looking at the 'blue ocean' view in jenkins build box).
So I'm back messing with dependencies. Current working theory is that the
exclusion added by the sub-issue addendum in HBASE-22059 was overbroad.
Instead, do explicit exclusions of what the invariant checker is complaining
about -- mostly old jersey references. We do this in the shaded mapreduce
client pom.xml.
This patch and the addendum HBASE-22059 against 2.1 were reverted. The
HBASE-22052 (this issue) patch against 2.2 which includes the HBASE-22059
addendum is still in place (and failing nightlies).
A new patch, 2.1.003 is a compound of what was reverted (HBASE-22059 and this
patch, HBASE-22052) plus more targeted exclusions in shaded mapreduce client
module.
> 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.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)
