Some committers in the Eclipse Scout team have started to investigate Mockito as mocking library. Currently EasyMock is used (version "[2.4.0,3.0.0)").
1) Latest version is 1.9.5. On Orbit: 1.8.4. Should we open a bug for an update?
2) Can we start using Mockito with Kepler or is this too late for introducing a new library?
3) I thing that we should not use 2 different libraries (it is possible, it can be a good transition solution, but the goal should be to use only one).
I was asked per email why we want to migrate. Here is my opinion on the situation:
We need a new Mocking Framework, to be able to mock Objects.
=> This is something the Scout Commiter wants to do in there Test. I got a question about it from Adrian Moser.
* Upgrade to EasyMock 3.x
* Change to Mockito
Both libs are not yet on Orbit.
(For Mockito, the version 1.8.4 in Orbit seems not to work with Tycho. See comment 1 in the bug).
To try the change, I have migrated the CellTest from EasyMock to Mockito. The effort to migrate a test is not big (the libraries are similar). The big effort is to get everything working in our CBI build.
I my opinion, the trend in the Eclipse Community is to use Mockito. The API of Mockito is more modern, simpler to learn and to use.
At the end I do not care what the final choice is (EasyMock 3.x vs Mockito).
With the Neon version, the Scout Project has moved away from OSGi and is no longer interested in dependencies hosted by the Eclipse Orbit project. We get our dependencies directly from Maven Central and we do not need them to be OSGi Bundles. Of course the IP (intellectual property) is still controled by the Eclipse Fundation.
In our master pom we depend from Version 1.10.19 see artifactIds pom "org.eclipse.scout.rt.platform.test" and "org.eclipse.scout.rt"