[ https://issues.apache.org/jira/browse/TINKERPOP-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314431#comment-15314431 ]
ASF GitHub Bot commented on TINKERPOP-1318: ------------------------------------------- Github user pluradj commented on the issue: https://github.com/apache/incubator-tinkerpop/pull/329 Yes, I ran integration tests with `-DincludeNeo4j` > java.lang.NoSuchMethodError: org/hamcrest/Matcher.describeMismatch > ------------------------------------------------------------------ > > Key: TINKERPOP-1318 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1318 > Project: TinkerPop > Issue Type: Bug > Components: test-suite > Affects Versions: 3.2.0-incubating, 3.1.2-incubating > Reporter: Jason Plurad > Assignee: Jason Plurad > Priority: Minor > > I don't recall specifically how to make this fail with {{gremlin-test}}, but > I did run into it at one point when writing a graph implementation. This blog > describes the issue and workaround. > https://tedvinke.wordpress.com/2013/12/17/mixing-junit-hamcrest-and-mockito-explaining-nosuchmethoderror/ > The error trace looks like this: > {noformat} > java.lang.NoSuchMethodError: > org.hamcrest.Matcher.describeMismatch(Ljava/lang/Object;Lorg/hamcrest/Description;)V > {noformat} > There is a dependency conflict created by an older version of {{hamcrest}} > coming out of {{mockito-all}}. The fix is to use {{mockito-core}} instead. > I'll submit a patch for this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)