Gradle - How to Fail on Major Version Conflict?

401 Views Asked by At

If my project requires dependency com.abc:xyz:1.2.0, and I have another dependency that transitively wants com.abc:xyz:2.0.0, this is a major problem because even if my project compiles, there could be behavior differences. For some reason in this case, Gradle assumes that using 2.0.0 will be no problem at all and chooses 2.0.0.

I want to fail in this case. I am aware of failOnVersionConflict(), but this raises errors even when the patch segments don’t match. How can I fail only when there is major version conflict?

Thanks

0

There are 0 best solutions below