Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
It is bad practice to use mockito-all because mockito-all include some of dependency's code in the package, which makes the dependency resolving not work expected and causes conflicting issues. For example, mockito-all include the code for hamcrest which may make the dependency point to the class in mockito-all instead of hamcrest-core, if there are any incompatible change in hamcrest, it will cause failure.
We should remove mockito-all and use mockito-core in the dependency for samza.
Attachments
Issue Links
- links to
