[
https://issues.apache.org/jira/browse/HBASE-20587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16775162#comment-16775162
]
Hudson commented on HBASE-20587:
--------------------------------
Results for branch master
[build #816 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/816/]: (x)
*{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/816//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/816//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/816//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Replace Jackson with shaded thirdparty gson
> -------------------------------------------
>
> Key: HBASE-20587
> URL: https://issues.apache.org/jira/browse/HBASE-20587
> Project: HBase
> Issue Type: Bug
> Components: dependencies
> Reporter: Josh Elser
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0, 2.2.0, 2.3.0
>
> Attachments: HBASE-20587-v1.patch, HBASE-20587-v2.patch,
> HBASE-20587-v3.patch, HBASE-20587.001.patch
>
>
> HBASE-20582 got me looking at how we use Jackson. It appears that we moved
> some JSON code from hbase-server into hbase-common via HBASE-19053. But,
> there seems to be no good reason why this code should live there and not in
> hbase-http instead. Keeping Jackson off the user's classpath is a nice goal.
> FYI [~appy], [~mdrob]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
