Björn Kautler

I didn't look into code yet, but well, they are most likely off-loading the actual repository management to the npm process. They do not support the Gradle syntax for dynamic...

I second OP, was about to report the same. I make my build fail if there are unresolved or outdated libraries. If I have for whatever reason the need to...

> If you specify a `dependencyUpdates.resolutionStrategy`, we only apply it to the [latest version query](https://github.com/ben-manes/gradle-versions-plugin/blob/4f0b7ce7b8c76531fcd0808c46a00b0a9b582d65/src/main/groovy/com/github/benmanes/gradle/versions/updates/Resolver.groovy#L127). No you are not or I'm getting you wrongly. Add e. g. `com.github.spotbugs:spotbugs:4.0.0-beta1` as dependency...

> Oh, I'm sorry - I meant we **don't** filter out hidden configurations. This was what I meant as a possible fix and pointing to the method to check on....

This project only has the root project, so yes I'm pretty sure :-)

It's not private but FOSS, just not ready for first push yet. :-D info output does not mention the ones that are missing or what am I looking for?

btw I already described minimal reproducer with which I just reproduced. `build.gradle` ```gradle plugins { id 'com.github.ben-manes.versions' version '0.20.0' } apply from: 'gradle/foo.gradle' ``` `gradle/foo.gradle` ```gradle buildscript { repositories {...

``` $ gw dependencyUpdate -i --console=plain 2>&1 | grep -A 10 Resolving Resolving versions-plugin-showcase project (root) buildscript with repositories: - __plugin_repository__Gradle Central Plugin Repository: PluginArtifactRepository Resolving versions-plugin-showcase project (root) configurations...

btw. little side question, do you have a plan when next release will come out? Besides this bug, I'd like to have the changed behavior of not printing the default...

Btw. just tried with a source dependency of master branch and nothing changed