[
https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16800097#comment-16800097
]
stack commented on HBASE-22052:
-------------------------------
So, undoing the htrace exclusions makes the shaded client it test pass. I
pushed the below and started a nightly #990 (I killed #989).
{code}
commit 7ca8578032c39d314b7877cdd23ca2a872510016 (HEAD -> 2.1.clean,
origin/branch-2.1)
Author: stack <[email protected]>
Date: Sun Mar 24 11:24:13 2019 -0400
HBASE-22052 pom cleaning; ANOTHER ADDENDUM
diff --git a/pom.xml b/pom.xml
index f157359382..92061b5f0a 100755
--- a/pom.xml
+++ b/pom.xml
@@ -2495,10 +2495,6 @@
<groupId>com.sun.jersey</groupId>
<artifactId>jersey-core</artifactId>
</exclusion>
- <exclusion>
- <groupId>org.apache.htrace</groupId>
- <artifactId>htrace-core</artifactId>
- </exclusion>
<exclusion>
<groupId>javax.servlet.jsp</groupId>
<artifactId>jsp-api</artifactId>
@@ -2592,10 +2588,6 @@
<groupId>com.sun.jersey</groupId>
<artifactId>jersey-core</artifactId>
</exclusion>
- <exclusion>
- <groupId>org.apache.htrace</groupId>
- <artifactId>htrace-core</artifactId>
- </exclusion>
<exclusion>
<groupId>commons-beanutils</groupId>
<artifactId>commons-beanutils</artifactId>
{code}
As a checkpoint, I've been working against branch-2.1. 2.2 has the problem also
but have been working on branch-2.1 only up to this. I applied 2.1.002 and then
the subissue HBASE-22059 to fix broken build. Subsequently I reverted both of
these patches. I then applied 2.1.003 and TWO addendums. Head of branch-2.1 git
log looks like this at the mo:
{code}
commit 7ca8578032c39d314b7877cdd23ca2a872510016 (HEAD -> 2.1.clean,
origin/branch-2.1)
Author: stack <[email protected]>
Date: Sun Mar 24 11:24:13 2019 -0400
HBASE-22052 pom cleaning; ANOTHER ADDENDUM
commit 73e40680c09726cb6454a6d9e65c837625090cc7
Author: stack <[email protected]>
Date: Sat Mar 23 17:19:58 2019 -0400
HBASE-22052 pom cleaning; ADDENDUM
commit fb56e4c454e0d3c4a980eaa7e738ded597cb92ea (2.1.clean2)
Author: stack <[email protected]>
Date: Fri Mar 15 00:27:13 2019 -0700
HBASE-22052 pom cleaning; filter out jersey-core in hadoop2 to match
hadoop3 and remove redunant version specifications
{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
> 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)
