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/08 12:31:20 UTC
[jira] [Updated] (TINKERPOP-1318) java.lang.NoSuchMethodError:
org/hamcrest/Matcher.describeMismatch
[ https://issues.apache.org/jira/browse/TINKERPOP-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Plurad updated TINKERPOP-1318:
------------------------------------
Fix Version/s: 3.2.1
3.1.3
> 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
> Fix For: 3.1.3, 3.2.1
>
>
> 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)