dependencyManagement section not scanned

[haraldott]

So when I trigger dependencyUpdates, I get a correct report with my artifacts in the dependencies section, but the dependencyManagement section is not being scanned.

dependencyManagement {
    imports {
        mavenBom 'io.spring.platform:platform-bom:1.1.1.RELEASE'
    }
}

[haraldott]

Even though this might appear to be related to https://github.com/ben-manes/gradle-versions-plugin/issues/97, it's not. because the dependencyManagement section is being ignored completely. What could be the reason for this?

[ben-manes]

Sorry that I missed this ticket twice. We scan every configuration's dependencies which these are not included in. The docs imply that they might be mapped into Dependency Constraints, which you can enable separate via checkConstraints.

PRs are welcome if you want to dig in for an improvement.

[leobut]

The checkConstraints option does unfortunately not work for this case.

But I found out the managed dependencies can be accesses during build through dependencyManagement.managedVersions, which gives back a map where the key is the identifier of the dependency and the value is the used version. See also: https://docs.spring.io/dependency-management-plugin/docs/current/reference/html/#working-with-managed-versions-programmatic-access

I really hope that this gets implemented at some point. It would make the plugin more compatible with the spring toolsuit and would also help us a lot ❤️ 😃