You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/06/03 17:08:59 UTC

[jira] [Commented] (TINKERPOP-1318) java.lang.NoSuchMethodError: org/hamcrest/Matcher.describeMismatch

    [ https://issues.apache.org/jira/browse/TINKERPOP-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314426#comment-15314426 ] 

ASF GitHub Bot commented on TINKERPOP-1318:
-------------------------------------------

GitHub user pluradj opened a pull request:

    https://github.com/apache/incubator-tinkerpop/pull/329

    use mockito-core instead of mockito-all to avoid hamcrest conflict

    https://issues.apache.org/jira/browse/TINKERPOP-1318

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/pluradj/incubator-tinkerpop TINKERPOP-1318

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-tinkerpop/pull/329.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #329
    
----
commit 27eedc478b58cd9dee571960091a3c6505f2379e
Author: Jason Plurad <pl...@us.ibm.com>
Date:   2016-06-03T17:05:10Z

    use mockito-core instead of mockito-all to avoid hamcrest conflict

----


> 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)