Jake Wharton
Jake Wharton
I would also like to record my support for having this be provided out of the box. Other Kotlin tooling, such as the binary compatibility validator, support ignoring declarations based...
And so the problem here is that Maven otherwise nonsensically chooses the nearest one, right? Rather than choosing the newest one, as one would expect. We merge the latest versions...
According to Maven's docs it should not: https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html > Maven picks the "nearest definition". That is, it uses the version of the closest dependency to your project in the tree...
Outside of the Maven semantics there is no actual conflict here, to be clear. The Kotlin stdlib promises this to be a compatible configuration (along with nearly every other library...
It's already fixed in the 5.0 alphas.
I'm not really involved in that, but since this occurrence is benign in practice I'm not sure they're going to do a whole release just for that. By the way,...
https://github.com/GradleUp/maven-sympathy https://github.com/usefulness/maven-sympathy
This came up a lot with Butter Knife where resource references would only exist in the generated code. I had good success reporting these to Google. It's a little different...
Actually as soon as I hit send I also remember this coming up when building view binding. I don't recall the outcome of that, though. Lint has a full call...