gradle-versions-plugin icon indicating copy to clipboard operation
gradle-versions-plugin copied to clipboard

Default dependencies aren't checked

Open gabrielittner opened this issue 7 years ago • 3 comments

I've got a Gradle plugin which creates a custom configuration and adds a default dependency to it using https://docs.gradle.org/current/javadoc/org/gradle/api/artifacts/Configuration.html#defaultDependencies-org.gradle.api.Action- dependencyUpdates does not check if that dependency has newer versions (it doesn't show up anywhere in the report).

gabrielittner avatar Jul 26 '18 08:07 gabrielittner

yeah, we don't do anything special regarding that. Currently we're using getAllDependencies, which is JavaDoc'd as the "declared dependencies". I guess that means it wouldn't include the defaults. I imagine this would be a slight change to Resolver to include it.

What would the negative side-effect of including them be? Potentially it would cause confusion of users not realizing where the dependency is coming from. We might need to indicate in the reports if its non-obvious

ben-manes avatar Jul 27 '18 05:07 ben-manes

Wouldn't the dependencies task be enough to figure out where it's coming from?

gabrielittner avatar Jul 27 '18 07:07 gabrielittner

@gabrielittner Do you have a repro for this? or is this ok to close?

jaredsburrows avatar May 16 '22 00:05 jaredsburrows