Unable to use JMock 2.6.0 with Java 8

[muminc]

Out of curiosity, tried to build an existing project (which uses 7) with Java 8 (source = 1.8, target=1.8) but I see many of these errors emitted by the Java 8 Compiler.

error: reference to with is ambiguous  both method with(Matcher<Float>) in Expectations and method with(Matcher<Double>) in Expectations match

[muminc]

I can confirm, if I build jmock (2.7.0-SNAPSHOT) and use this instead, Java 8 build works fine.

When will 2.7.0 be released?

[jh1234]

we have same problems. any changes?

[mread]

Also interested. What is the upgrade path for Java 8? We have 3000+ tests and I'm trying to find the least invasive way to get to a version of JMock that will support Java 8. The latest master gives me this error for tests are using @RunWith(JMock.class) - more than just deprecated perhaps?

java.lang.IllegalStateException: Mockery named 'mockery' is null
    at org.jmock.integration.junit4.JMock.mockeryOf(JMock.java:67)
    at org.jmock.integration.junit4.JMock.createTest(JMock.java:35)
    at org.junit.runners.BlockJUnit4ClassRunner$1.runReflectiveCall(BlockJUnit4ClassRunner.java:244)
...

[mikerimov]

I too had this problem but after looking at the code I suspect that it is an issue with the JDK 1.8 compiler. In my case the code that wouldn't compile was:

oneOf(something).method(with(anything()));

By adding a cast like so:

oneOf(something).method(with( (Matcher<Object>)anything() ) ) )

(Change the cast to whatever your argument type is)
And it then compiled for me. Also note that the eclipse compiler for me (Luna) compiles it correctly.

[mread]

... or use the new with primitive methods, e.g. with.floatIs(any(Float.class))

[bsiver]

Thanks @mread, I had some issues using parameterized types in expectations after upgrading to JDK 8:

oneOf(something).method(with(any(X.class)))

Started to generate a compiler error:
The method something(X<Y>) in the type Something is not applicable for the arguments (X).

Changing the expectation to

oneOf(something).method(with.is(any(X.class)))

fixed the compiler error.

[olibye]

Solved in 2.8.0, in maven central now.