[
https://issues.apache.org/jira/browse/HBASE-23052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934017#comment-16934017
]
Sean Busbey commented on HBASE-23052:
-------------------------------------
Second option: make it so [hbase-thirdparty's gson is in its own jdk7-compat
module PR#4|https://github.com/apache/hbase-thirdparty/pull/4]
I like this one even though it's a major version bump on hbase-thirdparty. We
don't have to downgrade anything and we aren't constrained on future dependency
upgrades unless gson eventually puts out a jdk8+ only version (it's currently
jdk6+)
> 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
>
> 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)
