[
https://issues.apache.org/jira/browse/HBASE-23052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-23052.
---------------------------------
Fix Version/s: thirdparty-3.0.0
Release Note:
<!-- markdown -->
HBase's internal use of GSON is now done in a stand alone module named
`hbase-shaded-gson` rather than as a part of the `hbase-shaded-miscellaneous`
module. The relocated fully qualified class names are still the same.
This internal artifact is also set to maintain JDK bytecode compatibility as
appropriate for use with branches-1 based releases in addition to the existing
use in later release lines.
Resolution: Fixed
> hbase-thirdparty version of GSON that works for branch-1
> --------------------------------------------------------
>
> Key: HBASE-23052
> URL: https://issues.apache.org/jira/browse/HBASE-23052
> Project: HBase
> Issue Type: Improvement
> Components: dependencies
> Affects Versions: thirdparty-2.2.1
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Blocker
> Fix For: thirdparty-3.0.0
>
>
> HBASE-23015 is buttoning up a needed move off of jackson 1 in branches-1.
> We've already got the implementation work in place to move onto the
> hbase-thirdparty relocated GSON, but we can't currently build because other
> dependencies included in the miscellaneous module is JDK8+ only and branch-1
> needs to work for jdk7.
> couple of options:
> * make the entire hbase-thirdparty repo work with jdk7
> * break out gson from the clearing house miscellaneous module and make *just*
> the new gson module jdk7 compatible
> * make a jdk7 compatible miscellaneous module and move gson over there (in
> case we decide to move branch-1 off of other problematic libraries e.g. guava)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
