[
https://issues.apache.org/jira/browse/HBASE-23052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934036#comment-16934036
]
Sean Busbey commented on HBASE-23052:
-------------------------------------
Third option: make a [jdk7 compat modules that has misc dependencies, starting
with gson PR#5|https://github.com/apache/hbase-thirdparty/pull/5]
I like this one too. Again we don't downgrade anything. We have a
straightforward path for adding to the things relocated for branches-1 and
handling the case if we need to diverge on the versions around for jdk7 and
jdk8.
it's unfortunate that we end up publishing multiple copies of the same
dependency before we actually need to though.
> 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)
