[ https://issues.apache.org/jira/browse/PHOENIX-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17824112#comment-17824112 ]
Nihal Jain commented on PHOENIX-6769: ------------------------------------- > If it does break them, then we may need to play with the mockito versions in > the HBase profiles. Yes this definitely makes sense. Will fall back to your suggested approach, if need be. Let's see how it goes. Will clone this JIRA for backport work. > Align mockito version with Hadoop and HBase > ------------------------------------------- > > Key: PHOENIX-6769 > URL: https://issues.apache.org/jira/browse/PHOENIX-6769 > Project: Phoenix > Issue Type: Bug > Affects Versions: 5.2.0 > Reporter: Andrew Kyle Purtell > Assignee: Istvan Toth > Priority: Major > Fix For: 5.2.0 > > > There is a well known incompatibility between old versions of mockito-all and > mockito-core and newer versions. It manifests as > IncompatibleClassChangeErrors and other linkage problems. The Hadoop > minicluster in versions 3.x embed mockito classes in the minicluster. > To avoid potential problems it would be best to align Phoenix use of mockito > (mockito-core) with downstreamers. HBase uses mockito-core 2.28.2 on > branch-2.4 and branch-2.5. (Phoenix is on 1.10.19.) I checked Hadoop > branch-3.3 and it's also on 2.28.2. > I recently opened a PR for OMID-226 to fix the same concern in phoenix-omid. -- This message was sent by Atlassian Jira (v8.20.10#820010)