Open GoogleCodeExporter opened 8 years ago
This could be a breaking change for existing users, we'll see if it's possible
to make that change in version 2.0.
Original comment by brice.du...@gmail.com
on 14 Mar 2013 at 7:45
Original comment by brice.du...@gmail.com
on 29 Apr 2013 at 4:09
Original comment by brice.du...@gmail.com
on 4 Dec 2013 at 3:03
[deleted comment]
[deleted comment]
Revert title change
Original comment by brice.du...@gmail.com
on 4 Dec 2013 at 4:12
Duplicate of
https://code.google.com/p/mockito/issues/detail?id=459&q=priority%3DHigh%20statu
s%3DAccepted ?
Original comment by marcin.g...@gmail.com
on 23 Dec 2013 at 7:51
Issue 459 has been merged into this issue.
Original comment by brice.du...@gmail.com
on 24 Dec 2013 at 11:54
I'm perfectly fine with updating to latest hamcrest in next major version
release of Mockito (2.0). For now, users should simply use mockito-core instead
of hamcrest. This way, the problem goes away.
Down the road I'd like mockito-core to stop depending on Hamcrest. We would
still offer integration, but mockito-core should use predicates that are not
susceptible to compatibility problems.
Original comment by szcze...@gmail.com
on 20 Apr 2014 at 3:10
For future reference there's a PR for that matter
https://github.com/mockito/mockito/pull/31
Original comment by brice.du...@gmail.com
on 21 Apr 2014 at 5:35
Original issue reported on code.google.com by
cloutier...@gmail.com
on 17 Feb 2013 at 7:48