-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes #2007 : Downgrade objenesis version for mockito-android #2024
Fixes #2007 : Downgrade objenesis version for mockito-android #2024
Conversation
Codecov Report
@@ Coverage Diff @@
## release/3.x #2024 +/- ##
==============================================
Coverage 84.88% 84.88%
Complexity 2703 2703
==============================================
Files 325 325
Lines 8198 8198
Branches 979 979
==============================================
Hits 6959 6959
Misses 968 968
Partials 271 271 Continue to review full report at Codecov.
|
Objenesis 2.6 version is now strictly defined in mockito-android. When mockito-core or mockito-kotlin is added as dependency, there will be version conflict for objenesis 2.6 and 3.1. For helping developer,
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This would work for me. @raphw WDYT?
Looks good to me, should we maybe still avoid the ASCII art? This can be difficult to read in some CI environments, I think the message by itself should be sufficient? |
I added asci art because when you have multiple conflicts, explanation text is between gradle messages. It might not be clear enough for inexperienced dev. That is just an assumption. Please feel free to adjust if it is needed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
WDYT about this?
Co-authored-by: Tim van der Lippe <TimvdLippe@users.noreply.github.com>
Hey folks! I hate to beat a merged horse, but I'm having a ton of trouble building locally and it seems to be related to this issue. Can anyone offer me some pointers? https://stackoverflow.com/questions/64341381/trouble-setting-up-mockito-for-local-development |
…android (mockito#2024)" This reverts commit 626d457.
check list
including project members to get a better picture of the change
commit is meaningful and help the people that will explore a change in 2 years
Fixes #<issue number>
in the description if relevantFixes #<issue number>
if relevantFixes #2007
After building, mockito android pom includes objenesis 2.6 while mockito-core has objenesis 3.1.
Locally build version is Tested with our internal project to verify fix.
pom of mockito-android.
Side note: I had problem with animal sniffer on release/3.x branch. I had to disable android api 24 signature check to compile the app.
Breaking changes solutions for android modules
Solution 1
If you have motkito-kotlin with mockito-android, exclude mockito-core from mockito-kotlin.
Solution 2
Don't add mockito-core with mockito-android
Solution 3
Use dependency resolution
in root build.gradle