You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-10Lines changed: 6 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,10 @@ The library has independent developers, release cycle and versioning from core m
38
38
-[Scalaz](/scalaz/src/test)
39
39
40
40
## Partial unification
41
-
If you're in Scala 2.11 or 2.12 you'll probably want to add the compiler flag `-Ypartial-unification`, if you don't you risk some compile errors when trying to stub complex types using the idiomatic syntax
41
+
If you're in Scala 2.12 you'll probably want to add the compiler flag `-Ypartial-unification`, if you don't you risk some compile errors when trying to stub complex types using the idiomatic syntax
42
+
43
+
## Notes for 1.18.0
44
+
We dropped support for Scala 2.11 and Java 8, as Mockito 5 dropped support for Java 8.
42
45
43
46
## Notes for 1.13.6
44
47
@@ -500,14 +503,14 @@ Of course you can override the default behaviour, for this you have 2 options
500
503
DefaultAnswers are also composable, so for example if you wanted empty values first and then smart nulls you could do `implicit val defaultAnswer: DefaultAnswer = ReturnsEmptyValues orElse ReturnsSmartNulls`
501
504
502
505
## Function Answers
503
-
`org.mockito.Answer[T]` can be a bit boilerplate-ish, mostly if you're still in Scala 2.11 (in 2.12 with SAM is much nicer),
506
+
`org.mockito.Answer[T]` can be a bit boilerplate-ish,
504
507
to simplify the usage for both versions is that we replaced it by standard scala functions, so instead of
0 commit comments