Conflicting versions of ArgumentsProcessor in mockito-core and mockito-scala

org.mockito.internal.invocation.ArgumentsProcessor class exists in both mockito-core and mockito-scala projects with different API.

Since classloading order is unreliable both versions can be loaded. As a result, when mockito-core’s version gets loaded first, there will be errors

java.lang.NoSuchFieldError: extractors
     at org.mockito.ReflectionUtils$.markMethodsWithLazyArgs(ReflectionUtils.scala:19)
     at org.mockito.MockitoEnhancer.mock(MockitoSugar.scala:122)
     at org.mockito.MockitoEnhancer.mock$(MockitoSugar.scala:119)

Please consider moving or renaming mockito-scala’s version.

[bbonanno]

Solved by #36 - mockito-scala 0.4.0

[bbonanno]

Well, it seems that it’s not consistent, I’ve created a dummy test project https://github.com/bbonanno/mockito-scala-as-dependency and it works as it is, but then if you add the mockito-core dependency, sometimes it works in SBT and not in the IDE and vice-versa depending in what order you put it, something surprising is that for some people it seems to work by putting the mockito-core dependency after the mockito-scala one (specs2 does something similar, so there are some StackOverflow posts about a very similar issue)

So what I did is to make the by-name feature in PR #19 and I added the instructions in the readme in how to enable the feature in case you needed it/wanna fight the class loader, if you use version 0.0.14 you will find the fix

I hope @mockitoguy and I can add the necessary support in mockito-core soon so we don’t rely on the class loader hack anymore.