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
0.26 have resolution issues #352
Comments
I have this error after updating to 0.26:
I'm using
Version 0.25 reported this instead:
|
Error 2:
Should have been found here https://jcenter.bintray.com/org/jetbrains/trove4j/trove4j/ |
Can you please provide minimal build files to debug with? The addition of evaluating dependency constraints seemed like a low impact value add so this is surprising and unfortunate. |
Tried to reproduce on a new app and can't, probably tied to tons of modules and everything, but I define all versions in a common place, so no idea how to move forward on reproduction :( |
Can you strip away the code and private details (like credentials) to a shareable build? |
You can try to debug on this project https://github.com/plastiqueapp/plastique, just change the version to 0.26.0 in the root |
Thanks, I reproduced the problem. I won't have time to debug much in the short-term. @anuraaga can you also take a look when you have time? |
Thanks for the report and repro! I have an idea of what the issue is will take a look. |
@ben-manes that version works without -DcheckConstraints and show the same issue with -DcheckConstraints so default behavior is properly restored thanks. |
Fixed, will release shortly. |
After updating from 0.25 to 0.26 the plugin returns wrong informations don't really know what you require to investigate.
For example it now returns :
When I do already use 2.1.0 and it's properly resolved by gradle at compile time.
Even stranger is that when using grade dependencies there's never a reference to version 2.0.0
All are correctly set to 2.1.0
+--- androidx.arch.core:core-common:{strictly 2.1.0} -> 2.1.0 (c)
The only other version is 2.0.1 that is correctly overiden.
The text was updated successfully, but these errors were encountered: