You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Jason Plurad (JIRA)" <ji...@apache.org> on 2016/06/01 18:11:59 UTC
[jira] [Created] (TINKERPOP-1318) java.lang.NoSuchMethodError:
org/hamcrest/Matcher.describeMismatch
Jason Plurad created TINKERPOP-1318:
---------------------------------------
Summary: 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.1.2-incubating, 3.2.0-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)