Ben Manes
Does the following work? ```gradle gradle dependencyUpdates -Drevision=integration ``` This plugin was written for Gradle 1.0, which was built on top of Ivy. The only option we had was to...
We use [use](https://github.com/ben-manes/gradle-versions-plugin/blob/a51972baeeffc8db8e86c066a40c0a5db9991887/src/main/groovy/com/github/benmanes/gradle/versions/updates/Resolver.groovy#L128) `Configuration.copyRecursive()` to clone the configuration and manipulate the dependency's version to a dynamic `+` resolution. That was originally a detached configuration, but we encountered bugs in Gradle's...
I'm not familiar with dependency constraints, but there was a [contribution](https://github.com/ben-manes/gradle-versions-plugin#constraints) that checks them. Does that help? #### Constraints If you use constraints, for example to define a BOM using...
That's strange since we don't treat configurations differently and simply iterate over all that are resolvable. You are welcome to investigate to figure out the root cause (see [Resolver](https://github.com/ben-manes/gradle-versions-plugin/blob/master/src/main/groovy/com/github/benmanes/gradle/versions/updates/Resolver.groovy)). This...
`revision` is an Apache Ivy concept, which Gradle was originally built upon. At that time, this was the only flag to control resolution. As few use `ivy.xml` metadata, it does...
We don't dictate a versioning scheme, that is defined by the dependency's metadata. As most use a Maven's POM, this only has a concept of snapshot and release, and the...
Please provide a minimal project. Usually it’s not having central but jcenter, etc in your repository list
This may depend on what repositories you have configured. When I run against mavenCentral() then it determines 2.8.0 is the latest, which matches the `maven-metadata.xml`. Since they did release in...
The `resolutionStrategy` concepts and parameter types come from Gradle, so there are limitations of how much we can enhance it. This does have the benefit by us delegating the resolution...
See #263, #335. The Gradle team has to provide assistance if they want to break compatibility for a 9yr old plugin or force it’s depreciation. Alternatively, they can incorporate the...