anyone know how to diagnose “downgrades” in depend...
# community-support
c
anyone know how to diagnose “downgrades” in dependency resolution? I have this dep that’s being
Forced
down from 2.38.0 to 2.36.0 (as per a build scan) and I don’t know why. Is there a way to see more info about why it is forced? I can’t see any usages of
resolutionStrategy.force
in any of the buildscripts or plugins at least.
solved: there was a plugin adding a dependency using
dependencies.enforcedPlatform(
with a bom
which had this dependency in it